Connect your Flipkart Marketplace seller account to EcomCentral using the Flipkart Seller API v3 with OAuth2 client-credentials authentication.
Authentication uses OAuth2 client_credentials — no browser login is required. A fresh bearer token is fetched per session using your application credentials. The token is not stored between requests; EcomCentral re-fetches it automatically on every operation.
app_id and app_secret. EcomCentral handles token acquisition transparently.
| Key | Required | Description | Example |
|---|---|---|---|
app_id |
Required | Application ID from the Flipkart Developer Portal. Used as the OAuth2 client_id in Basic auth to the token endpoint. | seller-app-12345 |
app_secret |
Required | Application Secret from the Flipkart Developer Portal. Used as the OAuth2 client_secret. | a1b2c3d4e5f6… |
sandbox |
Optional | Set to true to use the Flipkart sandbox environment (sandbox-api.flipkart.net) for testing. Omit or set to false for production. |
true |
appId or client_id for app_id;
appSecret or client_secret for app_secret.
| Operation | Method | Path | Notes |
|---|---|---|---|
| OAuth token | GET |
/oauth-service/oauth/token?grant_type=client_credentials&scope=Seller_Api |
Basic auth with app_id:app_secret; returns access_token |
| Search shipments (orders) | POST |
/v3/shipments/filter/ |
Filter by state (APPROVED, PACKED, READY_TO_DISPATCH); cursor-paged, no total count |
| Shipment detail | GET |
/v3/shipments?shipmentIds={id} |
Returns full shipment including address, order items, and fulfilment info |
| Self-ship dispatch | POST |
/v3/shipments/selfShip/dispatch |
Submit tracking ID and delivery partner code for self-fulfilled shipments |
Authorization: Bearer {token}. The base URL is
https://api.flipkart.net/sellers (production) or
https://sandbox-api.flipkart.net/sellers (sandbox).
| Status | Meaning |
|---|---|
APPROVED | Order confirmed by Flipkart; seller action required |
PACKED | Seller has packed the item |
READY_TO_DISPATCH | Ready for pickup by Flipkart logistics or self-ship dispatch |
DISPATCHED | Shipment picked up / dispatched |
DELIVERED | Item delivered to the buyer |
CANCELLED | Order cancelled (by buyer or Flipkart) |
RETURNED | Item returned by the buyer |
| Feature | Supported | Notes |
|---|---|---|
| View orders (shipments) | ✅ | Pre-dispatch shipments via POST /v3/shipments/filter/; cursor-paged, no total count |
| View order detail | ✅ | Full shipment: address, order items, prices, SKUs, fulfilment info via GET /v3/shipments?shipmentIds= |
| Add tracking (self-ship) | ✅ | Dispatch via POST /v3/shipments/selfShip/dispatch — carrier + tracking number required |
| Test connection | ✅ | Verifies OAuth token can be obtained; confirms API connectivity |
| View products (catalogue) | ❌ | No pageable catalogue endpoint — requires caller-supplied SKU IDs |
| Update stock quantity | ❌ | Requires a Flipkart locationId not available in the generic contract |
GET /listings/v3/{sku-ids}, which requires the caller to supply up to 10 SKU IDs.
There is no way to enumerate an unknown catalogue. Product access must come from a caller-supplied
SKU source (e.g. your own database or the Flipkart Seller Hub export).
POST /listings/v3/update/inventory require a Flipkart
locationId to target a specific fulfilment location. This location ID is not part of
the generic EcomCentral (sku, quantity) contract, so the operation is blocked rather than risking
an update to an unintended or blank location. If you need to update inventory, use
FlipkartClient::updateInventory($sku, $qty, $locationId) directly with a known location ID.
order_id must be the Flipkart shipmentId.
The self-ship dispatch endpoint operates on shipments, not order item IDs. When submitting tracking via
EcomCentral, supply the Flipkart shipmentId (e.g. OD1234567890) as the
order_id field. The shipmentId is visible in the order list and order detail panel.
The app_id or app_secret is incorrect or has been rotated. Verify both values
in the Flipkart Developer Portal and update the credential in EcomCentral.
Your Flipkart application has not been approved for Seller API access, or the scope
Seller_Api has not been granted. Check application status in the Developer Portal.
Flipkart manually reviews and approves Seller API applications — contact Flipkart support if
approval is pending.
The shipment filter returns only APPROVED, PACKED, and
READY_TO_DISPATCH pre-dispatch shipments. If there are no active shipments in those
states, the result will be empty. This is expected behavior.
Set sandbox: true in your credentials to route requests to
sandbox-api.flipkart.net. Sandbox credentials are separate from production credentials
and must be obtained from the Flipkart Developer Portal sandbox environment. Remove or set
sandbox: false when going live.