What we proposed
On the morning of March 23 2026, we sent ONDC's leadership team a proposal: add AMBULANCE as a vehicle category under the existing TRV10 transit specification. The proposal included six enum codes covering the full operational spectrum — Mini BLS for stable transport, BLS for emergency response, ALS for cardiac and critical care, Ventilator for ICU-level transit, Mortuary for last-mile dignity transport, and Organ Transport for time-critical procurement. Each enum mapped to a specific medical context, equipment specification, and crew certification. The proposal arrived at 11 AM IST. ONDC's response came at 4:23 PM the same day.
“let's add AMBULANCE as a category in TRV10.”
What ONDC said
ONDC's protocol leadership replied same-day with: "Let's add AMBULANCE as a category in TRV10." Two weeks later the protocol team confirmed in writing on April 15 2026 that the AMBULANCE enums were being added to the public developer guide. A call on April 21 finalized the technical integration path.
“We are taking this up to get it updated in the developer guide and are adding the enums as mentioned.”
What we built
Ten Beckn endpoints. All live. All on api.ambugo.help. The full transaction lifecycle — search, select, init, confirm, status, track, cancel, update, rating, support — runs through the same ONDC-compliant interfaces every other network participant uses. We're not asking ONDC to build us a special API. We built to their spec, the spec we helped write.
Where we are now
April 21 technical call complete. ONDC customer-care Gmeet complete. Subscriber registration on ONDC pre-prod environment in progress (preprod.ambugo.help). Pramaan certification next. Public TRV10 v2.1 with ambulance enums — ONDC's release schedule, not ours.