Connect your Jumpseller store to EcomCentral using API login key and auth token — no OAuth flow required.
login key and
authtoken are appended as query params on every API request.
No OAuth flow or session management is needed —
credentials are sent directly as ?login=…&authtoken=….
| Key | Required | Description | Example |
|---|---|---|---|
login |
Required | API login key from Admin Panel → Account → API section | abc123xyz |
authtoken |
Required | 32-character API auth token from the same API section | a1b2c3d4e5f6789… (32 chars) |
api_login for the login key;
auth_token or token for the auth token.
| Operation | Method | Endpoint |
|---|---|---|
| Test connection | GET | /store/info.json |
| List orders | GET | /orders.json?page=P&limit=N |
| Orders count | GET | /orders/count.json |
| Order detail | GET | /orders/{id}.json |
| Update order tracking | PUT | /orders/{id}.json body: {"order":{"tracking_number","tracking_company","shipment_status"}} |
| List products | GET | /products.json?page=P&limit=N |
| Products count | GET | /products/count.json |
| Product detail | GET | /products/{id}.json |
| Update product stock | PUT | /products/{id}.json body: {"product":{"stock":N,"stock_unlimited":false}} |
[{"order":{...}},{"order":{...}}] for orders,
[{"product":{...}}] for products./count.json endpoint that returns {"count":N}.?login={login}&authtoken={authtoken} as query params.
All paths end in .json.
| Status | Color | Meaning |
|---|---|---|
| Pending Payment | Blue | Order placed but payment not yet received |
| Payment Received | Blue | Payment confirmed; awaiting fulfillment |
| Processing | Blue | Order is being prepared for shipment |
| Paid | Green | Payment received and order confirmed |
| Shipped | Green | Order has been shipped to the customer |
| In Transit | Blue | Shipment is on the way |
| Delivered | Green | Shipment delivered to the customer |
| Awaiting Pickup | Amber | Order ready for customer to collect |
| On Hold | Amber | Order paused; requires manual action |
| Completed | Green | Order fully complete |
| Fulfilled | Green | All items have been fulfilled |
| Cancelled | Red | Order was cancelled |
| Refunded | Red | Payment was refunded to the customer |
| Failed | Red | Payment or processing failed |
| Feature | Supported | Notes |
|---|---|---|
| View orders (paginated) | ✅ | Order ID, date, status, total with currency |
| View order detail | ✅ | Customer info, billing address, shipping address, line items, tracking info |
| Add / update tracking | ✅ | Tracking number + carrier; sets shipment_status to Shipped automatically |
| View products (paginated) | ✅ | Product ID, SKU, name, price, stock (∞ for unlimited) |
| View product detail | ✅ | Full product data including images, categories, description, store link |
| Update stock quantity | ✅ | By product_id; sets stock_unlimited to false and stock to requested quantity |
| Stock unlimited flag | ✅ | Products with stock_unlimited: true display stock as ∞ |
| Test connection | ✅ | Returns store name, URL, currency, and country from /store/info.json |
The login key or authtoken is incorrect, or the token was regenerated after saving
the connection. Go to Account → API in your Jumpseller admin panel, copy the current
credentials, and update the connection in EcomCentral.
All Jumpseller API paths must end in .json — e.g. /orders/123.json.
If you see 404 errors, verify the base URL is exactly https://api.jumpseller.com/v1
with no trailing slash. Custom base URLs are only needed for self-hosted or sandbox environments.
Jumpseller enforces per-minute rate limits on their API. EcomCentral pages results (default 50 per request, max 100) to reduce call frequency. If you hit rate limits during large syncs, wait a minute and retry. Contact Jumpseller support to request a higher limit for your plan.
Verify that https://api.jumpseller.com is reachable from your EcomCentral server.
EcomCentral connects over HTTPS with peer verification enabled.