Sapa Moto

Changelog & versioning

What changes within v1, how long old versions live and what changed when.

Versioning policy

  • The version is in the path: /v1/.... The api_version of webhooks is v1.
  • Within a version we make only backward-compatible changes: new endpoints, new optional request fields, new response fields, new webhook events, new error and reason codes, new enum values in fields documented as open lists (status, kind, reason_code).
  • Your client must ignore unknown fields and treat unknown codes by their HTTP status.
  • Breaking changes (removing or renaming a field, changing a type or the meaning of a field) only come with a new version (/v2). The previous version keeps working at least 6 months after the new one is released; we announce the date by e-mail to the administrators of every connected organization and on this page.
  • The OpenAPI specification of the current version is always downloadable: English, Russian.

Changelog

2026-10-23 — v1

First public version of the Partner API:

  • quotes with a 10-minute price, delivery slots, pickup points;
  • orders: create (idempotent, unique external_id), batch of up to 100, read by id or external_id, list with cursor pagination, change by the И2 4.3 rules, ready signal, cancellation with fee, Kaspi QR payment status;
  • courier position and ETA (/track), proof of delivery with a temporary photo link (/proof);
  • balance; webhook endpoints and signed webhooks (X-Sapa-Signature, HMAC-SHA256) with retries for 24 hours, suspension and held events;
  • sandbox with a virtual courier and five scenarios;
  • rate-limit headers X-RateLimit-Limit / X-RateLimit-Remaining.

Planned

  • POST /v1/pickup-points — create pickup points through the API.
  • GET /v1/statements — the register of charges and cash-on-delivery offsets for a period.

These docs are built from the platform's OpenAPI specification. Download OpenAPI