canonical: https://jentic.com/apis/seller.flipkart.com/seller-flipkart

# Seller Flipkart Flipkart Seller API

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.

## For AI agents

Programmatically generate access token, check token expiry. Covers 12 operations with basic, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Generate access token
- Check token expiry
- Filter shipments
- Get shipment details
- Confirm shipment dispatch

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'generate access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/oauth-service/oauth/token` | Generate access token |
| GET | `/oauth-service/oauth/token/expiry` | Check token expiry |
| POST | `/sellers/v3/shipments/filter` | Filter shipments |
| GET | `/sellers/v3/shipments/{shipmentId}` | Get shipment details |
| GET | `/sellers/v3/shipments/{shipmentId}/labels` | Get shipment labels |
| GET | `/sellers/v3/shipments/{shipmentId}/invoices` | Get shipment invoices |
| POST | `/sellers/v3/shipments/dispatch/confirm` | Confirm shipment dispatch |
| POST | `/sellers/v3/shipments/{shipmentId}/cancel` | Cancel a shipment |

## Key resources

- **Oauth Service** — Operations for oauth service
- **Sellers** — Operations for sellers

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 60 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 35 / 100
  - AI Discoverability: 70 / 100
- **View full report:** https://jentic.com/apis/seller.flipkart.com/seller-flipkart/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Flipkart Seller API by hand means exchanging basic credentials for a bearer token through its oauth-service endpoint, refreshing that token as it expires, and building each shipment request yourself. Through Jentic you install once, import Flipkart Seller from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The Flipkart Seller API puts the shipment id in the URL path (`/sellers/v3/shipments/{shipmentId}/...`), so a rule can pin your agent to reading one shipment's labels and invoices and nothing else. You choose the operations it may call, so writes like confirming dispatch or cancelling a shipment are not included unless you add them.
- **Credential handling:** Your Flipkart Seller credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'fetch a shipment's labels' or 'filter shipments', and Jentic returns the matching Flipkart Seller operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Flipkart Seller API use?

The Flipkart Seller API uses basic, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

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

Yes. Jentic One is self-hosted, so your own rules decide which of the API's operations and which credentials the agent may use. Because each shipment id sits in the URL path (`/sellers/v3/shipments/{shipmentId}/...`), you can pin the agent to reading one shipment's labels and invoices and nothing else. Writes such as confirming dispatch or cancelling a shipment stay out of reach unless you explicitly add those operations.