Domains & Specifications
ONDC's contract is a layered specification: the Beckn base protocol, an ONDC network extension on top, and per-domain specifications that adapt the protocol for each sector. Every network participant implements these specs — they define the API calls, schemas and enumerations for search, order, fulfilment, payment and grievance. Browse the domains below; each links to its open-source specification repository.
Core protocol
The Beckn base + ONDC network extension that every domain builds on (ONDC-Protocol-Specs, protocol-base, protocol-network-extension).
Retail (RET)
B2C and B2B retail commerce specifications (ONDC-RET-Specifications).
Logistics (LOG)
Domestic and international B2B logistics specifications.
Mobility (TRV)
Interoperable ride-hailing and transport (mobility-specification).
Financial Services (FIS)
Lending, insurance and other financial use cases (ONDC-FIS-Specifications).
ONEST & more
Services (SRV), ONEST (social/skilling), Agriculture (AGR) and the Registry & NTS specs.
Specification domains
Core Protocol
4Mobility (TRV)
1Retail (RET)
1Financial Services (FIS)
1Network Technical Specs (NTS)
1Agriculture (AGR)
1Metro / Enterprise (MEC)
1ONEST (Social/Skilling)
1Registry
1Services (SRV)
1Links
FAQ
What is Beckn?
Beckn is the open protocol ONDC is built on — a set of decentralised commerce APIs. ONDC layers a network extension and domain specs on top of it.