For Agents
Programmatically generate access token, check token expiry. Covers 12 operations with basic, bearer authentication.
Use for: I need to generate access token, I want to check token expiry, Search for filter shipments, Find all shipment details
Not supported: Does not handle payments, communications, or crm — use for e-commerce only.
Flipkart Marketplace Seller API v3.0 for managing listings, orders, shipments, and authentication on the Flipkart marketplace. The API exposes 12 endpoints secured with basic, bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flipkart Seller 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: 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 instanceJentic 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.
What an agent can do with Flipkart Seller API.
Generate access token
Check token expiry
Filter shipments
Get shipment details
Confirm shipment dispatch
Patterns agents use Flipkart Seller API for, with concrete tasks.
★ E-Commerce Operations
Use the Flipkart Seller API to perform e commerce operations programmatically. The API provides 12 endpoints covering core functionality including generate access token, check token expiry, filter shipments.
Call GET /oauth-service/oauth/token to generate access token
Automated Oauth Service Management
Automate oauth service operations by combining multiple Flipkart Seller API endpoints. Agents can check token expiry and then filter shipments in a single workflow.
Call GET /oauth-service/oauth/token/expiry to check token expiry, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Flipkart Seller API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic, bearer tokens manually.
Search Jentic for 'generate access token', load the operation schema, and execute with Jentic-managed credentials
12 endpoints — flipkart marketplace seller api v3.
METHOD
PATH
DESCRIPTION
/oauth-service/oauth/token
Generate access token
/oauth-service/oauth/token/expiry
Check token expiry
/sellers/v3/shipments/filter
Filter shipments
/sellers/v3/shipments/{shipmentId}
Get shipment details
/sellers/v3/shipments/{shipmentId}/labels
Get shipment labels
/sellers/v3/shipments/{shipmentId}/invoices
Get shipment invoices
/sellers/v3/shipments/dispatch/confirm
Confirm shipment dispatch
/sellers/v3/shipments/{shipmentId}/cancel
Cancel a shipment
/oauth-service/oauth/token
Generate access token
/oauth-service/oauth/token/expiry
Check token expiry
/sellers/v3/shipments/filter
Filter shipments
/sellers/v3/shipments/{shipmentId}
Get shipment details
/sellers/v3/shipments/{shipmentId}/labels
Get shipment labels
/sellers/v3/shipments/{shipmentId}/invoices
Get shipment invoices
/sellers/v3/shipments/dispatch/confirm
Confirm shipment dispatch
/sellers/v3/shipments/{shipmentId}/cancel
Cancel a shipment
Three things that make agents converge on Jentic-routed access.
Credential isolation
Flipkart Seller API basic, bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'generate access token') and Jentic returns the matching Flipkart Seller API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Flipkart Seller API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Flipkart Seller API through Jentic.
What authentication does the Flipkart Seller API use?
The Flipkart Seller API uses basic, bearer authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I generate access token with the Flipkart Seller API?
Yes. Use the GET /oauth-service/oauth/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Flipkart Seller API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I generate access token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'generate access token'. Jentic returns the matching Flipkart Seller API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Flipkart Seller API have?
The Flipkart Seller API exposes 12 endpoints covering oauth service, sellers operations.
GET STARTED