intelligent.pageDocs

Swiggy Instamart

Vendor purchase-order channel, not a marketplace: no public brand API, so integration is a supplier portal, emailed POs, GRN and payments.

Swiggy Instamart is the quick commerce arm of Swiggy, launched in 2020 and run as a separate business line under its own chief executive. It delivers groceries and everyday goods in minutes from dark stores. For a brand, Instamart is a wholesale customer rather than a sales channel: stock is bought in against a purchase order, and Instamart sets the retail price and decides which dark stores carry the item. Swiggy publishes partner portals for restaurants and delivery riders but none for brands or suppliers, and there is no public API for Instamart supply.

At a glance

What it is

Swiggy's corporate pages describe the company as a unified convenience platform with food delivery from 2014, Instamart and Genie from 2020, Swiggy One membership from 2021, Minis from 2022, the Dineout acquisition in 2022 and Bolt in 2024. Instamart is named as the quick commerce service. Swiggy competes here with Blinkit and Zepto, and the three are usually treated as one segment by order management vendors.

The supply model is inventory led. A brand ships stock into an Instamart warehouse against a purchase order; Instamart then distributes to dark stores and sells to consumers on its own account. The brand's revenue recognised against Instamart is the value received at goods receipt, net of trade terms, not consumer sell-out.

Warning

The counterparty on the invoice may not be the Swiggy entity a brand expects. Indian foreign direct investment rules constrain how an e-commerce platform with foreign capital can own inventory, and Indian quick commerce companies have historically interposed separate seller or wholesale entities to hold stock. Confirm the exact legal entity, GSTIN and state of supply on the vendor agreement before designing the load, and carry it as channel_account_id. This structural point was not verified against a Swiggy-published source.

API access

None for brand supply. Swiggy's about page links exactly two partner surfaces: "Partner with us" at partner.swiggy.com for restaurant partners and "Ride with us" at ride.swiggy.com for delivery partners. No brand, supplier or vendor link is published. A direct fetch of partner.swiggy.com on 2026-09-21 returned only the page title, "Swiggy Partner App", because the site is client rendered, but nothing in its surrounding navigation suggests it covers Instamart supply.

Swiggy does operate developer-facing integrations in the restaurant business, where point of sale vendors connect menus and orders. That is a different programme with a different counterparty and it does not extend to Instamart brand supply. Do not reuse restaurant partner documentation for an Instamart connector.

What aggregator documentation shows:

  • Unicommerce lists Swiggy Instamart in its published integrations catalogue, describing it as ten-minute grocery delivery.
  • Unicommerce's page for the comparable Blinkit connector states the mechanism: "an innovative email parsing solution, automating the journey from PO receipt to order creation", with the flow given as purchase order received by email, auto forwarded to Unicommerce, order created. That page names Blinkit, Zepto and Swiggy Instamart together as its quick commerce coverage.
  • EasyEcom markets a quick commerce operation but its public pages describe outcomes rather than the mechanism per channel.

The reasonable engineering conclusion as of 2026-09-21 is that automating Instamart means parsing purchase order documents and portal exports, not calling endpoints.

How a brand gets onboarded

Commercial, not technical, and unverified against a Swiggy-published source: reach an Instamart category buyer, usually through an existing distributor, a broker or a trade contact; sign a supply agreement covering cost price, margin, listing and visibility fees, returns liability and payment terms; complete vendor master registration with GSTIN, PAN, bank details and registered addresses per state of supply; then receive supplier portal credentials for purchase orders, appointments and reports.

Authentication

Not published. Portal access is a username and password issued to the brand contact. No token endpoint, scope model, credential rotation or multi-entity handling is documented, which is a real problem for a brand supplying under several GSTINs.

Objects we can read

Nothing through a documented interface. The vendor-visible object set, named in vendor vocabulary rather than invented field names:

Purchase orders

PO number, issue date, delivery-by or expiry date, destination facility, and line items carrying the brand SKU, an Instamart item code, ordered quantity, cost price and tax. Delivered as a document by email and visible in the portal. No published schema, so no sample is given here.

Appointments, goods receipt and payments

Delivery into an Instamart facility generally needs a booked slot, and missing the window pushes the line into short supply. Goods receipt records received quantity against ordered quantity, plus rejections for damage or short shelf life; the ratio across a period is the fill rate a buying team manages the brand against, normally the single metric the relationship turns on. Remittance or payment advice then reconciles invoices against receipts, less deductions for trade terms, damages, marketing and listing fees, on a cadence set by the agreement.

What is not available

Consumer orders, end customer identity, per dark store stock on hand and listing status are not exposed to vendors through any documented route. Sell-out visibility in this segment is typically sold back to brands as a paid analytics product rather than provided as vendor data.

Writing back: listings, price and stock

Not available. Instamart owns the listing and the retail price. The brand controls only the negotiated cost price. New SKU introduction, content and imagery go through the category manager and the portal's item setup flow, not through a feed you can drive.

Webhooks and notifications

None. Email is the notification channel. The workable design is a dedicated mailbox with a document parser, watched continuously rather than on a slow schedule, because purchase orders carry a delivery-by date and late detection costs fill rate directly.

Rate limits and pagination

Not applicable. Portal exports are manual downloads. Where an aggregator sits in the middle, its own API limits govern.

Mapping to the unified model

The unified model has no purchase order table. Decide once whether Instamart purchase orders live in orders with the caveats below, or in a separate procurement table, and apply it consistently across all three quick commerce vendors.

Gaps and open questions

  • Swiggy publishes no supplier or brand partner page, so the onboarding steps above are inferred from how the segment works and are not sourced from Swiggy.
  • Whether Instamart offers any vendor API to large suppliers is unverified. Aggregator sales engineers will know before it is public.
  • The legal entity that issues the purchase order, and whether it differs from Swiggy Limited, was not verified, nor was the purchase order document format or whether the supplier portal offers a structured export.
  • swiggy.com and partner.swiggy.com are client rendered and returned almost nothing to the fetcher. Revisit with a browser-based fetch. Web search was unavailable, so no news coverage was reviewed.

Sources