Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflipkart.com%2Fflipkart" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflipkart.com%2Fflipkart" | 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.

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

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Flipkart Marketplace 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

/orders/dispatch

Dispatch a batch of orders

POST

/returns/{returnId}/approve

Approve a buyer return

POST

/returns/{returnId}/reject

Reject a buyer return

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Flipkart Marketplace API by hand means running its OAuth2 flow for scoped seller tokens, mapping work across the /orders, /listings, and /returns hierarchies, and handling retries yourself. Through Jentic you install once, import Flipkart from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Flipkart scopes to the seller account through the OAuth grant and identifies individual orders, SKUs, and returns per request rather than pinning one owned resource, so limit the agent to the operations it needs, such as order search and shipment dispatch, and leave return approval or rejection out of the allowed set unless required. You choose which of the 11 operations it may call.

Credential isolation

Your Flipkart OAuth2 credential is stored once, encrypted, by your own Jentic One instance and exchanged for a scoped token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'dispatch a Flipkart order' or 'search orders', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without navigating the /orders, /listings, and /returns hierarchies.

FAQs

Specific to using Flipkart Marketplace 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 run it through Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Flipkart Marketplace API?

Yes. Because you run Jentic One self-hosted, your own rules decide which of the 11 Flipkart operations the agent may call and which stored credential it uses. You can allow read and fulfilment work such as POST /orders/search, POST /orders/labels, and POST /orders/dispatch while leaving the return decisions at POST /returns/{returnId}/approve and POST /returns/{returnId}/reject out of the allowed set. The OAuth grant already scopes access to your seller account, and your operation allowlist narrows it further to exactly what the agent needs.

Flipkart Marketplace API

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

Official vendor OpenAPI document · agent-readyE CommerceOrder Managementoauth211 EndpointsREST

For Agents

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

Use for: List all Flipkart orders received in the last 24 hours, Look up a specific order by its order ID, Update the price for SKU SKU12345, Generate shipping labels for today's pending shipments

Not supported: Does not handle catalogue creation, advertising campaigns, or seller payouts - use for Flipkart marketplace listing updates, order processing, shipment dispatch, and returns decisions only.

The Flipkart Marketplace API gives sellers programmatic access to their seller account on Flipkart, India's largest e-commerce marketplace. It covers product listings keyed by SKU, order search and lookup, shipment dispatch and labelling, and the returns workflow including approval and rejection. The endpoints align to the day-to-day operating loop of a Flipkart seller: list, sell, ship, and handle returns.

Jentic One on Github View OpenAPI Document

Connect the Flipkart Marketplace API to your agent

Capabilities

Start building with Flipkart Marketplace API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Flipkart Marketplace API