Event Sign-Up Report: Missing Address and Phone Number

Retrieving the buyer/recipient shipping address for Square Online orders with a DIGITAL fulfillment via API

I’m trying to build a report of Event Signups — an attendee roster (name, email, phone, and address) for events we sell through Square Online — and I’m stuck on pulling the recipient address. Hoping someone can point me to the right field or endpoint.

Setup: Seller uses Square Online. Customers buy event tickets (a catalog item with date variations). At checkout the buyer fills in a required Contact section (phone, email, first/last name) and a required Address section (country, street, apt, city, state, postal). In the Seller Dashboard, the order’s “Other details” panel shows a Recipient name, a recipient Phone, and a full Address. The Dashboard Orders CSV export likewise includes Recipient Name / Email / Phone / Address / Postal / City / Region columns, all populated.

Problem: I can’t retrieve that recipient address (or recipient phone) through the API. Here’s everything I checked for the same order:

Orders API (RetrieveOrder / SearchOrders) — the fulfillment comes back with no recipient and no address:

"fulfillments": [
  { "uid": "...", "type": "DIGITAL", "state": "PROPOSED" }
]

No shipment_details / delivery_details / recipient, and no order-level address.

Payments API (RetrievePayment) — billing_address and shipping_address only carry the name (occasionally a postal_code), never street/city/state, and no phone:

"billing_address":  { "first_name": "[REDACTED]", "last_name": "[REDACTED]" },
"shipping_address": { "first_name": "[REDACTED]", "last_name": "[REDACTED]" },
"buyer_email_address": "[REDACTED]"

Customers API (RetrieveCustomer) — the linked profile’s address has only country, even though it was updated on the order date:

"address": { "country": "US" }

The profile phone also differs from the recipient phone shown on the order in the Dashboard.

Order Custom Attributes (ListOrderCustomAttributes) — returns empty.

Reporting API — the Orders cube exposes customer_id (good) and lists tax_destination_postal_code / tax_destination_state as dimensions, but querying those two returns OPTIMIZER_INTERNAL_ERROR.PLAN_STRUCTURE ... referenced attributes not found. The ItemSales entity has item_variation_name but no customer_id.

Expected: the buyer-entered recipient Address + Phone (the same values shown in the Dashboard and in the Orders CSV export) to be available on the order — presumably as a fulfillment recipient.

Questions:

  1. For Square Online orders with a DIGITAL fulfillment, where is the buyer’s recipient Address and recipient Phone stored, and how do I read it via API?
  2. What is the source of the Recipient Address / Postal / City / Region columns in the Dashboard Orders CSV export? Is there an API field that maps to them?
  3. Is the reduced billing_address / shipping_address on the payment (name only) expected behavior, or should the full address be present?

Happy to share a specific order ID privately. Thanks!

It looks like you’ve checked all the right endpoints. If the Dashboard and CSV include the recipient address but the APIs don’t, it’s likely that data isn’t exposed through the public API. I’d contact Square Support with a sample order ID to confirm whether this is a current limitation or if there’s another endpoint available.

Thank you. I will give it a try!

This is a Square Online API limitation. The recipient address and phone shown in Dashboard/CSV don’t seem to be exposed through the public Orders, Payments, or Customers APIs for DIGITAL fulfillments. The CSV data is likely from Square’s internal Online order system. You may need Square support to confirm if there’s another endpoint or if these fields are currently unavailable via API.

Yes, these fields are unfortunately unavailable via API.

Hi @ashley-square

Thanks for the confirmation that recipient address and phone shown in Dashboard/CSV are not exposed through the public Orders, Payments, or Customers APIs for DIGITAL fulfillments.

It would be great if:

  1. It could be eventually exposed via API

2). The Square Team responsible for Events creates an Events Sign-Up Report that we could view in real-time via Square Dashboard.

Thanks!