Flipkart Marketplace API

Name: Flipkart Marketplace API API
Brand: Flipkart Marketplace API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder Managementoauth211 EndpointsREST

For Agents

Manage Flipkart marketplace listings, search and look up orders, dispatch shipments, generate shipping labels, and approve or reject returns.

Connect the Flipkart Marketplace API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flipkart Marketplace API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Flipkart Marketplace API API.

Update a product listing keyed by SKU including price and inventory levels

Search and filter seller orders by date, status, or shipment criteria

Look up a single order by orderId to read line items, status, and shipment fields

Generate shipping labels and dispatch shipments for a batch of orders

GET STARTED

Start building with Flipkart Marketplace API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Flipkart Marketplace API API for, with concrete tasks.

★ Daily order processing for Flipkart sellers

Sellers run a daily order-processing job that calls /orders/search to find new orders, /orders/labels to generate shipping labels, and /orders/dispatch to mark them shipped. The same loop drives carrier handover and updates the buyer's order page on Flipkart automatically.

Search for orders with status 'approved' from the last 24 hours, generate labels for them, and call dispatch with the resulting shipment IDs

Listing and price management

Merchandising teams keep Flipkart listings in sync with the master catalog by calling /listings/v3/{skuId} for each SKU that changes price or stock. The endpoint accepts updates per SKU, which fits well with rule-based repricers and inventory-sync tools that reconcile multiple sales channels.

Update the price and stock count for SKU SKU12345 to match the master catalog values

Returns approval workflow

Customer-service teams use /returns/{returnId}/approve and /returns/{returnId}/reject to action buyer return requests, with a structured reason captured for each decision. /returns lists open cases for triage and supplies the data needed for refund and restocking workflows downstream.

List all returns awaiting decision, approve those that match the standard policy, and reject any with damaged-package evidence

AI agent marketplace operator

An AI ops agent uses Flipkart through Jentic to react to marketplace events: shipping orders, repricing SKUs, and processing returns. Jentic returns the right Flipkart operation per intent, so the agent does not need to memorise the /orders, /listings, and /returns path hierarchies before issuing calls.

Process the day's pending Flipkart orders end-to-end: search, label, dispatch, and post a summary count

Key Endpoints

11 endpoints — the flipkart marketplace api gives sellers programmatic access to their seller account on flipkart, india's largest e-commerce marketplace.

METHOD

PATH

DESCRIPTION

PATCH

/listings/v3/{skuId}

Update a SKU listing

POST

/orders/search

Search seller orders

GET

/orders/{orderId}

Look up a single order

POST

/orders/shipments

Manage shipments for orders

POST

/orders/labels

Generate shipping labels

POST

/orders/dispatch

Dispatch a batch of orders

POST

/returns/{returnId}/approve

Approve a buyer return

POST

/returns/{returnId}/reject

Reject a buyer return

PATCH

/listings/v3/{skuId}

Update a SKU listing

POST

/orders/search

Search seller orders

GET

/orders/{orderId}

Look up a single order

POST

/orders/shipments

Manage shipments for orders

POST

/orders/labels

Generate shipping labels

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Flipkart OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive scoped tokens at execution time, so seller client secrets never enter the agent context.

Intent-based discovery

Agents search Jentic by intent such as 'dispatch a Flipkart order' and Jentic returns the matching operation with its input schema, removing the need to navigate the /orders, /listings, and /returns hierarchies manually.

Time to first call

Direct Flipkart integration: 2-3 days for OAuth setup, label and dispatch payload assembly, and returns reason mapping. Through Jentic: under 1 hour to search, load the schema, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Amazon Marketplace Web Service API

Amazon is the alternative global marketplace where sellers run an equivalent listings, orders, and returns loop

Pick Amazon for sellers operating outside India or alongside Flipkart for cross-marketplace order handling

Alternative

eBay Sell Fulfillment API

eBay's Sell Fulfillment API covers shipment and order fulfilment for eBay sellers

Pick eBay when sellers also list on eBay and need a unified fulfilment agent across marketplaces

Complementary

Shopify Admin API

Shopify provides the seller's own storefront that often syncs inventory with Flipkart listings

Use Shopify alongside Flipkart when the seller operates a direct-to-consumer storefront and needs unified inventory

FAQs

Specific to using Flipkart Marketplace API API through Jentic.

What authentication does the Flipkart Marketplace API use?

The Flipkart Marketplace API uses OAuth 2.0. Through Jentic the OAuth client credentials are held in the encrypted vault and exchanged for short-lived access tokens at execution time, so the seller's client secret never enters the agent context.

Can I update a SKU price with the Flipkart Marketplace API?

Yes. PATCH /listings/v3/{skuId} with the new price and inventory fields to update a single SKU listing.

How do I generate shipping labels for orders?

Call POST /orders/labels with the order or shipment IDs and the API returns the labels needed for carrier handover. Pair this with POST /orders/dispatch to mark the orders shipped.

What are the rate limits for the Flipkart Marketplace API?

Flipkart does not publish a single global rate limit in the spec. Limits are applied per seller account. Treat 429 responses as the source of truth and back off using the Retry-After header.

How do I dispatch Flipkart orders through Jentic?

Search Jentic for 'dispatch a Flipkart order', load the schema for POST /orders/dispatch, and execute the call with shipment IDs. Install with pip install jentic and sign up at https://app.jentic.com/sign-up.

Can I approve or reject buyer returns with this API?

Yes. POST /returns/{returnId}/approve and POST /returns/{returnId}/reject decide on each return request with a structured outcome reason.