SKUTOPIA API
Welcome to the SKUTOPIA API. This is the single, opinionated entry point for programmatic access to the SKUTOPIA platform.
High Level Overview
As of 2026 we are expanding the use cases this API supports. Expect new capabilities to become available throughout 2026 across:
- Analytics and read operations
- MCP tools
- Purchase orders (stock transfers to SKUTOPIA)
- Inventory
- Products
- New webhooks for operations on the above
Versioning and deprecation
We version our APIs to set clear expectations around stability and change management.
- v0 APIs: Breaking changes are allowed. We will give advance notice to consumers, but breaking changes may occur.
- v1 APIs: 12-month deprecation policy. We will not introduce breaking changes to v1 endpoints without 12 months of notice.
Reliability and Processing Guarantees
We provide exactly-once processing guarantees through idempotent operations and careful request handling. This ensures that duplicate requests do not create duplicate orders or cause unintended side effects.
Callers are expected to implement retries for timeouts or server failures with exponential backoff. It is necessary to supply the appropriate idempotency keys when retrying requests to avoid duplicate operations.
Idempotent Operations
All API operations are idempotent by design. Making the same request multiple times produces the same result without side effects. In some cases, an explicit idempotency key is required to achieve this guarantee. Provide this in the Idempotency-Key header.
Eventual Consistency
We use an eventually consistent processing model. This gives us:
- Immediate acknowledgment. The API returns a success response when a request is received.
- Processing guarantee. If a successful response is returned, we guarantee the operation will be processed eventually.
- Webhook notifications. Use webhooks to track operations and state changes.
- No polling required. Do not poll for status updates. Rely on webhook events for real-time notifications.
Security
The API uses the OAuth2 Client Credentials flow for authentication. You will receive a client ID and secret from SKUTOPIA.
Treat these as secrets. Never expose them in client-side code or version control. You are expected to obtain and maintain a valid access token. Refresh it before expiration to ensure uninterrupted API access.
Webhooks
Webhooks notify clients of events that occur throughout the SKUTOPIA API. Webhooks do not use OAuth2 authentication. Instead, they are secured using a pre-shared key and signature verification.