Connect your ACEShop store to EcomCentral using the REST API with API key authentication.
https://myshop.example.com)Authorization: Bearer {api_key} and X-Api-Key: {api_key} headers
on every request. No OAuth flow is required.
| Key | Required | Description | Example |
|---|---|---|---|
shop_url |
Required | Your shop's root URL (no trailing slash) | https://myshop.example.com |
api_key |
Required | API key from ACEShop admin Settings → API | ace_live_abc123… |
shopUrl or base_url for the URL;
apiKey or key for the API key.
| Operation | Method | Endpoint |
|---|---|---|
| Test connection | GET | /api/v1/store |
| List orders | GET | /api/v1/orders?page=P&per_page=N |
| Order detail | GET | /api/v1/orders/{id} |
| Add tracking | PUT | /api/v1/orders/{id}/tracking |
| List products | GET | /api/v1/products?page=P&per_page=N |
| Product detail | GET | /api/v1/products/{id} |
| Update stock | PATCH | /api/v1/products/{id} with { stock: N } |
{ "data": [...], "meta": { "total": N, "page": P } }.
EcomCentral reads the data array and meta.total for pagination.
| Feature | Supported | Notes |
|---|---|---|
| View orders (paginated) | ✅ | Order number, date, status, total |
| View order detail | ✅ | Line items, shipping address, existing tracking |
| Add tracking number | ✅ | PUT to order tracking endpoint; carrier + URL optional |
| View products (paginated) | ✅ | SKU, name, price, stock quantity |
| View product detail + variants | ✅ | Variant list from variants field |
| Update stock quantity | ✅ | PATCH product with { stock: N } |
| Test connection | ✅ | Returns store name, domain, currency |
The API key is incorrect or API access is disabled. Verify the key in ACEShop admin → Settings → API. Ensure API access is enabled for your account.
Check the shop_url — it must include the protocol (https://) and
match your store's domain exactly. Self-signed SSL certificates on test installs may
need to be trusted on the EcomCentral server.
ACEShop field names may vary between versions. EcomCentral renders fields defensively with multiple fallback paths. If a field is consistently blank, the API response may use a non-standard field name — contact ACEShop support for the field documentation specific to your version.