Skip to content
RE-ZIP API Docs

January 2026 Deprecation Notices

Section titled “GET/PUT /{shops/partners}/{id}/logo”

These endpoints are deprecated. Logos have been folded into the general concept of account files.

The GET has a direct equivalent in GET /{shops/partners}/{id}/files/type/logo.

The PUT is replaced by POST /{shops/partners}/{id}/files/upload and POST /{shops/partners}/{id}/files/finish.

POST /{shops/partners}/{id}/files

Section titled “POST /{shops/partners}/{id}/files”

This endpoint is deprecated due to scalability concerns. Please move to POST /{shops/partners}/{id}/files/upload and POST /{shops/partners}/{id}/files/finish.

PUT /{shops/partners}/{id}/files/{file_id}

Section titled “PUT /{shops/partners}/{id}/files/{file_id}”

This endpoint is deprecated due to scalability concerns, and is no longer needed: file uploads of a given type for a given account are idempotent. It can also be replaced by POST /{shops/partners}/{id}/files/upload and POST /{shops/partners}/{id}/files/finish.

value field on a voucher

Section titled “value field on a voucher”

The value field on the voucher struct, in endpoints like GET /me/rewards, is deprecated in favour of a new field named value_data. value_data is an object containing everything you need to display this information in a localization-friendly way.

drop_point_fk, latitude, longitude, and address fields on drop point locations

Section titled “drop_point_fk, latitude, longitude, and address fields on drop point locations”

On the drop point location struct, in endpoints like GET /drop_points/{id}/locations:

  • drop_point_fk has been renamed to external_id to match other structs.
  • address has been renamed to shipping_address to match other structs, and a billing_address has been introduced.
  • latitude and longitude have been moved into shipping_address, matching the schema of other account types.

POST /me/access-token return schema

Section titled “POST /me/access-token return schema”

The schema returned by /me/access-token has changed from the bare access token in text/plain to an application/json body that includes it. This remains backwards compatible for now, since the Authorization header still accepts the entire JSON blob, but the old behaviour should be considered deprecated.

POST /shops/{id}/vouchers/batches

Section titled “POST /shops/{id}/vouchers/batches”

The voucher_pool_id field should be considered required. Omitting it is deprecated.

GET /me/rewards

Section titled “GET /me/rewards”

This request applies a default filter of type = Voucher when none is specified. This behaviour is deprecated.