January 2026 Deprication Notices
GET/PUT /{shops/partners}/{id}/logo
Section titled “GET/PUT /{shops/partners}/{id}/logo”These endpoints have been deprecated as logos have been folded into the general concept of account files.
The GET has a direct corollary in GET /{shops/partners}/{id}/files/type/logo.
The PUT has been replaced with 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 as been 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 as been deprecated due to scalability concerns aswell as not being needed. File uploads of a given type for a given account are idempotent. Thus this endpoint can also be readily 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 have been depricated in favour of a new field named value_data which is an object which contains all data you’d need to display this information in an localization friendly manor
drop_point_fk, latitude, longitude and address field on drop point locations
Section titled “drop_point_fk, latitude, longitude and address field on drop point locations”the drop_point_fk field on the drop point location struct in endpoints like GET /drop_points/{id}/locations has been renamed to external_id to match other structs
the address field on the drop point location struct in endpoints like GET /drop_points/{id}/locations has been renamed to shipping_address to match other structs, and a billing_address as been introduced
the latitude and longitude fields have been moved to shipping_address aswell to match the schema of other account types
POST /me/access-token return schema
Section titled “POST /me/access-token return schema”the schema return by /me/access-token has changed from being the bare access token in text/plain to a application/json which includes it. This remains backwards compatable for now as the Authorization header does accept the entire json blob. However this 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, and omiting it should be considered depricated.
GET /me/rewards
Section titled “GET /me/rewards”this request has a default filter of type = Voucher if none is specified, this behaviour should be considered depricated.