API endpoints
API endpoints
Ecart API exposes three API versions. All use the same base URL (e.g. https://api.ecartapi.com). Choose the version that fits your use case.
| Version | Use case | Behaviour |
|---|---|---|
| v1 | Raw response from the ecommerce | Returns the ecommerce's native format. Use when you need platform-specific behaviour. Example path: /api/v1/customers. |
| v2 | Unified response (recommended) | Same structure across all ecommerces. The API calls the ecommerce and maps the response to a unified schema. Example path: /api/v2/orders. |
| v3 | Centralized data, faster, higher limits | Same unified contract as v2, but reads from a centralized database instead of calling the ecommerce on each request. Data is kept up to date via webhooks or periodic requests. Example path: /api/v3/products. |
Base URL and paths
| Item | Value |
|---|---|
| Base URL (example) | https://api.ecartapi.com |
| Example paths | /api/v1/..., /api/v2/..., /api/v3/... for the respective version. |
Use the store access token as Bearer in the Authorization header for all three versions. See Store access token for details.
For detailed endpoint reference per platform, see the API Reference section in the docs.
Updated 30 days ago