UpdateBooking rejects appointment_segments on card-paid bookings since ~2026-07-17 (reservation_segments: "no order line item with uid …")

Questions
1

Since 2026-07-17 13:30 UTC, `UpdateBooking` rejects any request that
includes `appointment_segments` when the booking is tied to a COMPLETED, card-paid
order. The identical call succeeded for months before that date with no change on
our side. Time-only updates (omitting `appointment_segments`) still succeed.

2

Could you share your app ID?

3

sq0idp-EbrDXMV5425dwA3suHafeQ

4

It looks like a regression on the API side. Since nothing changed in your requests and only updates with appointment_segments started failing after July 17, it’s worth reporting to support with request IDs and before/after examples. Hopefully they can confirm and fix it quickly.

6

isn’t this where I would report it ? is there another place for square dev support?

7

I’m still having this issue. Were you able to look into it ?

9

Thanks for the detailed report, and yes, this is the right place to flag it. The owning engineering team has been notified with a full root-cause analysis and is working on a fix. In the meantime, the workaround you’ve already found is the recommended one: omit appointment_segments from UpdateBooking requests on completed, card-paid bookings unless you need to change them.

10

Hi, just following up. When should I expect to hear back ? I would love to provide more details to help speed things up.

11

Thanks for your patience as we sort this out.

Quick update for the thread: this turned out to be related to the calendar/team-member issue you reported in your other thread. Both trace back to the same underlying data inconsistency on certain paid/completed bookings. The UpdateBookingrejection (“no order line item with uid”) is the write-side symptom of the same problem.

A fix for the root cause has been deployed, and we’re now working on correcting the previously affected bookings on your accounts (we have your merchant IDs from our DM- thank you!!). Once that data correction is complete, UpdateBookingcalls with appointment_segments on those bookings should succeed again, no changes needed on your side.

I’ll follow up via our DMs once the correction has run. If you see this rejection on any booking created after this week, please flag it with the booking ID, as that would be new information for us.