July 2026 Deprecation Notices

latitude and longitude on partner locations

On the partner location struct and its write endpoints — GET/POST /partners/{id}/locations and PATCH /partners/{id}/locations/{location_id} — the top-level latitude and longitude fields are deprecated.

Coordinates now live inside address, matching the shape used by other account types:

• When reading, use address.latitude and address.longitude. The top-level fields are still emitted but are derived from address and should be ignored.
• When writing, send address.latitude and address.longitude. The top-level fields are still accepted and merged into address for now, but that behaviour is deprecated.

string[] body on POST /shops/{id}/vouchers/batches/{batch_id}/codes

This endpoint historically accepted a bare array of code strings (["ABC123", "DEF456"]). That form is deprecated in favour of an array of objects ([{ "code": "ABC123", "link": "https://…" }]), which also lets you attach a per-code link. The response echoes whichever shape you send. Migrate to the object form; the string form remains accepted for older clients.

Default filter[type] on GET /me/rewards

When filter[type] is omitted, GET /me/rewards defaults to filter[type]=Voucher and returns vouchers only. Relying on this implicit default is deprecated — always pass an explicit filter[type] (e.g. Voucher or Ticket). This was first flagged in the January 2026 notice and is now reflected in the endpoint’s OpenAPI description.