Protocol Workbench

ONDC Protocol Workbench

Test your ONDC app without a real partner.

You bring your app. The workbench plays the other side. It checks every message your app sends and replies the way a real partner would.

Setup used on this site: domain ONDC:RET11 · version 1.2.0 · use case F&B · flow Search_and_Custom_Menu_(Full_Catalog_City) · the workbench running on a local machine.

My app is a…

your appBuyer app
workbench playsSeller app

● message from your app   ● message to your app. Watch which one moves first.

    The parts

    Eleven boxes, one job each.

    Click a box to see what it does and who it talks to. Or press Follow a message to watch one message travel through the workbench.

    Showing: buyer app test. Change it at the top of the page.

    Swipe sideways to see the whole map.

    ONDC messages Running the test Storage Outside / at build time

    Click any box on the map.

    The checks

    Every message from your app passes five gates.

    Onix runs them in this order. The first gate that fails stops the message, and your app gets a . Pick a message and send it.

    1Is a test waiting?Links it to your session
    2Right shape?Fields and types
    3Follows the rules?
    4Fits this test?Right step, on time
    5Real signature?Key from the
    ✓Saved and recorded

    After an ACK, Onix passes the message to the Mock. The Mock then runs the step's own check, the .

    Where data is kept

    Short-term in Redis. Long-term in MongoDB.

    Click a box to see who writes it, who reads it, and how long it lasts.

    Redis short-term · port 6379

    MongoDB long-term · through DB Service

    What's next

    Three full walk-throughs, step by step.