JioMart is Reliance Retail's mass market marketplace, spanning groceries, general merchandise, electronics and fashion, and backed by the largest physical store network in India. For a seller it behaves less like Amazon and more like a retail chain that happens to have a website: JioMart decides which of your locations serves an order, JioMart issues the invoice, and the rules about when a cancellation is still allowed are tied to the invoicing and dispatch steps rather than to a status you control. There is no public developer portal and no published API reference. An integration surface clearly exists, since the major order management vendors connect to it, and the credential they ask for is a username and password issued by the JioMart category manager. This page records the mechanism and the operating constraints from those vendor knowledge bases.
At a glance
What it is
JioMart is owned by Reliance Retail and is part of the same group as AJIO, though the two are separate seller systems with separate credentials and no shared integration. Its breadth is the point: groceries and daily needs are the origin, but the catalogue now covers electronics through the Jio digital business, fashion, home and general merchandise. Sellers include both third party marketplace sellers and Reliance's own retail formats, and in the grocery lane there is a kirana partner model where local stores participate in fulfilment.
Two structural facts drive the connector design. First, JioMart routes the order to a location. Unicommerce states it directly: "Location/facility allocation for the orders would be routed by JioMart." The seller registers their facilities and maps them, but JioMart decides which one serves a given order. A connector cannot choose the shipping location and should not try.
Second, the invoice is the pivot point for cancellation rules. Seller cancellation is prohibited once the order has been invoiced. Partial customer cancellation is blocked after invoicing. Full customer cancellation is restricted once dispatch status has been pushed. So the state machine is not a simple ladder you can walk backwards, and a connector has to treat invoicing as a one way door.
Order splitting is not allowed.
API access
There is no self serve route and no application form on a developer site. The sequence, as far as it is documented:
- Be an onboarded JioMart seller.
- Ask the JioMart category manager for API credentials. Unicommerce's setup page names the source twice: the username and the password are both "provided by the JioMart's category manager".
- Receive JioMart location ids for each facility that will fulfil.
- Configure the credential pair and a JSON map of JioMart location id to internal facility code.
No API version, deprecation calendar, changelog or official SDK could be found. No Postman collection is published.
One observable technical detail: the seller portal's own login is an OAuth 2.0 authorisation code flow. Fetching seller.jiomart.com redirects to identity.seller.jiomart.com/sso/oauth/authorize with a client_id, a redirect_uri, response_type=code and a state parameter. That is Reliance's identity management system securing the web portal. It does not follow that the seller API uses OAuth, and no source says it does. The credentials the aggregators ask for are a plain username and password, which is the opposite signature. Do not assume the portal's SSO is the API's auth.
This page contains no base URL, path or request body, because none is published. Scope a conversation with the JioMart category manager, or an integration through Unicommerce, EasyEcom, Vinculum, Browntape or Ginesys, all of which hold working credentials and expose documented APIs of their own.
Authentication
Three configuration values:
- Username, issued by the JioMart category manager.
- Password, issued by the JioMart category manager.
- JioMart store map, a JSON object of JioMart location id to internal facility code, in the form
{"jiomartLocationId1":"FacilityCode1"}.
There is no published token endpoint, expiry, refresh step or scope model. As with AJIO and Nykaa, the shape of the setup form is the evidence: a fixed pair entered once is a static credential, not OAuth.
Multi account handling is one credential pair per seller, with the facility map carrying the multi location dimension rather than the credential. That is a different shape from AJIO, where the credential itself is per location.
Objects we can read
No endpoint, parameter, pagination model or sample response is published for any object. The operations below are confirmed by a production integration.
Orders
Order sync is supported. Orders arrive already allocated to a JioMart location, so the first thing a connector does with an order is resolve the JioMart location id to an internal facility using the configured map.
Order splitting is not allowed, so one order stays one fulfilment unit.
Sample response not published. Field names not published.
Order items
Lines exist inside the order. No separate order items endpoint is described. Because splitting is prohibited, lines cannot be dispatched independently.
Products and listings
Catalogue sync is supported. Unicommerce records a JioMart operating practice worth knowing: the JioMart team asks its sellers to populate the SKU code in the JioMart catalogue with the same value as the SKU in the seller's own system, so that mapping happens automatically without manual matching. If that convention has been followed, the channel SKU and the internal SKU are the same string, which removes the hardest part of most marketplace onboardings. If it has not, expect manual mapping.
No listing creation or update API is described.
Inventory
Inventory sync is supported and facility wise inventory is enabled by default, so JioMart holds a quantity per location rather than a single pool. Each facility in the store map carries its own number. No batch size, cadence or reconciliation endpoint is published.
Shipments and tracking
The split of responsibility is specific. The invoice is fetched from JioMart, while the invoice code comes from the seller's own system. The manifest is generated by the seller's system, not by JioMart, which is the opposite of AJIO. Dispatch status is then synced back to JioMart.
No AWB, carrier or tracking event feed is described for JioMart in any source read here, which is a notable difference from AJIO, where both the AWB and the courier partner name are documented as syncing back.
Returns and cancellations
Status sync covers cancelled, delivered and return cases. On the return side there is a write back: when the return is completed in the seller's system, a notification is sent to JioMart to complete the CIR or RTO case. CIR is the customer initiated return, RTO is the return to origin of an undelivered parcel. So returns are two way, unlike AJIO where they do not sync at all.
The cancellation rules are the constraint to encode:
- the seller cannot cancel after invoicing
- a partial customer cancellation cannot be applied after invoicing
- a full customer cancellation cannot be applied after dispatch status has been pushed
Payments and settlements
No settlement or payout API is described. Panel reports only.
Customers
Customer details arrive with the order, since the seller packs and a delivery address is needed. Nothing is published about masking. Treat everything received as PII.
Locations
Locations are JioMart location ids, issued by JioMart and mapped to internal facilities in the integration. No location listing API is described. Allocation of an order to a location is JioMart's decision, not the seller's.
Writing back: listings, price and stock
Stock is the confirmed write path, through facility wise inventory sync.
Dispatch status is written back, and it is a consequential write because it closes the window for a full customer cancellation.
Return completion is written back, as the CIR or RTO completion notification.
Price has no described API path. Plan for the seller portal.
Listings have no described creation or update API. Catalogue upload is a portal workflow with a bulk template. Catalogue sync in the vendor integrations reads listings out.
Webhooks and notifications
None published. No source describes JioMart pushing anything to a seller endpoint, and the integrations are described in terms of syncs triggered from a channel summary page, which is a poll.
A reasonable cadence, absent published limits: order sync every ten to fifteen minutes, inventory sync on change with a daily full reconciliation, catalogue sync daily, status sync tied to the order sync. Push dispatch status promptly, because the cancellation window depends on it.
Rate limits and pagination
Not published. No numbers, no headers, no pagination model, no sandbox. Ask the category manager alongside the credentials.
Mapping to the unified model
Gaps and open questions
- No base URL, path, method, header or body is public for any call.
- No tracking data is documented. Whether JioMart returns an AWB and carrier, as AJIO does, is unresolved, and it matters for any delivery reporting.
- The seller portal uses an OAuth 2.0 SSO while the integrations use a username and password. Whether an OAuth path exists for the API, and whether it is preferable, is worth asking.
- Whether JioMart provisions API credentials to a seller building their own connector, or only through approved vendors, is not stated.
- No settlement API, no rate limits, no sandbox, no versioning, no changelog.
- The kirana partner fulfilment model and the JioMart Digital electronics lane may have different integration surfaces. Nothing read here distinguishes them.
- CIR and RTO are named in the vendor documentation without definition. The expansions given here are the standard Indian logistics meanings, not a JioMart source.
Sources
- JioMart Seller Portal, official, login only, observed on 2026-09-21 to redirect to an OAuth 2.0 authorisation code SSO at
identity.seller.jiomart.com/sso/oauth/authorize - Unicommerce: integration with JioMart, aggregator, source of the username and password from the category manager, the JioMart location id to facility mapping, the order, inventory and catalogue sync list, the cancelled, delivered and return status sync, the prohibition on order splitting, the cancellation rules around invoicing and dispatch, the JioMart controlled location allocation, the invoice fetch, the manifest generation split and the CIR and RTO completion notification