Skip to documentation
Browse documentation
For AI agents

Connect your agent to live platform data.

Open in

Product fulfillment

Inspect one JioMart product at a PIN and distinguish local quick-commerce listings from national-catalogue fallback.

Capability ID jiomart.fulfillment.get
Maximum runtime 30 seconds
View raw

POST /execute Shared execution endpoint

Input parameters

Provide exactly one of slug, numeric product_id or supported /p/ url. For a PIN-specific check, provide a six-digit pincode or the same PIN inside location; conflicting PIN values are rejected.

Although location can carry city, state and coordinates, this fulfillment comparison is postcode-scoped. Treat the PIN as the location identity for the check.

location object optional
location.city string optional

City name.

location.latitude string optional

Latitude in decimal degrees.

location.longitude string optional

Longitude in decimal degrees.

location.pincode string optional

Postal code (PIN) that sets the delivery location.

location.state string optional

State or region name.

pincode string optional

Postal code (PIN) that sets the delivery location.

Example 560001
product_id string optional

Product identifier.

Example 7511070
slug string optional

Slug from the page URL.

url string optional

Public URL of the page to fetch.

Response

Successful output is returned in results[0].data.

serviceable means at least one JioMart local store serves the PIN. It does not by itself mean the requested product is locally listed.

journey: quickcommerce is a listing scoped to resolved serving stores. journey: standard is national-catalogue presence and is not delivery confirmation. sellable is reserved for a store-matched local listing; catalogue sellability is retained separately when available.

ETA is attached only when a matching serving-store response supports it. Inventory count, store-open state and delivery slots should not be treated as product-specific evidence when they are null or empty.

Illustrative sample The example response is shown in the response panel.

Illustrative output fields

Values illustrate one response. Read the guidance above for missing values and limits; fields can vary with the requested operation and the data available.

PathObserved typeExample
availability_flags object 5 fields
availability_flags.kirana_1p boolean true
availability_flags.kirana_3p boolean false
availability_flags.rrl_fc boolean true
availability_flags.rrl_store boolean true
availability_flags.seller_3p boolean true
delivery_message string Delivery in 28 mins
delivery_slots array 0 items
eta_minutes integer 28
fulfiller object 3 fields
fulfiller.id string 2147
fulfiller.name string Reliance Retail Limited (400710)
fulfiller.number string 3PEGURHKFC01
fulfillment_metadata_scope string national_catalog
inventory_count null null
journey string quickcommerce
listed boolean true
pincode string 560001
product_id string 7511070
quick_delivery_tagged boolean true
sellable boolean true
serviceable boolean true
slug string india-gate-super-basmati-rice-1-kg-mffmvi-7511070
store_ids array 1 items
store_ids array 1 items
store_open null null

Execution behavior

A 200 response completed inline. A 202 response was queued; poll GET /jobs/:id until the job reaches completed or failed.

Overview, pricing and sample data for every endpoint: JioMart API