A unified way to connect, one set of conventions, and one place for documentation — partners and developers integrate with Atasuai's modules according to their own permissions. Delivery is in pre-release, and the rest are coming online.
Every module follows the same authentication, conventions, and documentation. Learn one, and you can use them all.
For delivery partners: receive dispatched jobs, deliver to the door (intra-city / inter-city), and hand packages over to partner carriers. Supports integrating your own system or using our managed back office.
For sellers integrating on their own: pull orders, update order status, and sync prices and inventory (following the Kaspi marketplace model). Currently in development.
Not a pile of scattered endpoints crammed under one domain — but a truly unified foundation.
All modules share one OAuth 2.0 way to connect, but each partner receives only the scopes they should have — delivery partners get only deliveries:*, sellers get only orders:*, with no overreach.
All modules share the same specification: versioned paths, idempotency keys, cursor pagination, RFC 7807 errors, and HMAC-signed webhooks. Learn it once, apply it everywhere.
Unified developer documentation, an interactive API reference, and an isolated sandbox at sandbox.open.atasuai.com (Planned, certificate not yet ready). Every new module launches right here.
Create API credentials in the partner back office, or have an Atasuai account manager enable them during onboarding — you are only authorized to access the modules that match your identity (delivery partners cannot see order data). Agent (delivery-partner) credentials are temporarily disabled; seller credentials work normally. Integrate delivery today; when you genuinely need more modules, add the corresponding scopes to your credentials later.
