Install Jentic One Beta

Connect the Flipkart Seller API to your agent

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fseller.flipkart.com%2Fseller-flipkart" | 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%2Fseller.flipkart.com%2Fseller-flipkart" | 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 Seller API.

Generate access token

Check token expiry

Filter shipments

Get shipment details

Confirm shipment dispatch

Use Cases

GET STARTED

Start building with Flipkart Seller API

Explore with Jentic One

View OpenAPI Document

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

Key Endpoints

12 endpoints — flipkart marketplace seller api v3.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

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

Seller Flipkart Flipkart Seller API

Name: Flipkart Seller API
Brand: Flipkart Seller API
Availability: InStock

AI ReadinessAI-Aware (B-)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceOrder Managementbasic, bearer12 EndpointsREST

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

37%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Flipkart Seller API to your agent

Capabilities

Use Cases

Start building with Flipkart Seller API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Seller Flipkart Flipkart Seller API

Jentic AI Readiness Score

Flipkart Seller API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness