In the previous blog, we learned about what ONDC is and how it can revolutionize Digital E-Commerce.
But to bring this revolution, there must be an ONDC ecosystem consisting of the ONDC network, the Buyer app, and the Seller app deployed on the ONDC network.
What does this statement mean that applications should be deployed on the ONDC network? And how exactly can this be done?
In this blog, we will discuss how can we deploy our seller app and buyer app on the ONDC network, and we will see the most popular APIs associated with ONDC. This is what an ONDC-enabled e-commerce network will look like.
ONDC uses asynchronous APIs that buyer applications and seller applications must integrate in order to use the network.
The buyer’s application calls the search API to find the offer. Once this call is sent, the buyer’s application receives a unique ID in response. Now the network calls the on_search hook of the buyer application to provide the search result from the sellers.
Listed below are the APIs starting with on_ are callback/web-hook APIs implemented in ONDC along with their callbacks:-
The APIs as on_search fall in the category of searching or discovery. The select, init and confirms fall under the category of order APIs, status, track, and update, while cancel APIs fall under the category of fulfilment criteria.
The rating and cancel fall under support API. Now, these are the APIs that are integrated into sellers’ or buyers’ applications. But there are some more network infrastructure API, for example:-
The below diagram explains the best flow of how these APIs and callbacks work for buyers’ and sellers’ apps-
The following APIs will be used at the seller’s end -
That’s it, folks! Hope you liked both of these articles and found them insightful. For further queries, feel free to reach out at Habilelabs.