Flipkart

Flipkart is one of India's largest e-commerce marketplaces, headquartered in Bengaluru and majority-owned by Walmart. For third-party developers and sellers it publishes the Flipkart Marketplace Seller API (v3), an OAuth 2.0 protected REST API hosted at api.flipkart.net that covers listing management, order and shipment management, returns, and report generation, plus an Order Management Notification (webhook) service for order events. Flipkart also runs an affiliate program with its own tooling. This profile captures Flipkart's public developer surface: the seller API, its OAuth authentication and scopes, conventions, lifecycle, and domain security posture.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

How we profile Flipkart

Each block below is one kind of artifact we hold for Flipkart. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 1

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Flipkart Marketplace Seller API

The Flipkart Marketplace Seller API (v3) lets sellers and integration partners manage listings, orders, shipments, returns, and reports on the Flipkart marketplace programmatica...

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

flipkart-mcp.yml

MCP SERVER

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Flipkart Notifications Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Flipkart Authentication

oauth2 · 1 scheme

SECURITY

Flipkart Domain Security

TLSv1.2 · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Flipkart Scopes

2 scopes · clientCredentials/authorizationCode

2 scopes

SCOPES

Resources

Every other property we hold for Flipkart — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

← All providers · Data indexed from github.com/api-evangelist/flipkart · machine-readable index on apis.io