Webhooks
Real-time lifecycle events. Not yet available.
COMING SOON. Ryde does not deliver outbound webhooks yet. Until it does, poll the resource — get_ride, get_food_order, get_delivery, get_task — which is the authoritative state in any case. This page describes the contract being built so you can design for it; do not implement a receiver against it yet.
Design for these properties
- At-least-once delivery. The same event can arrive more than once — persist event ids and ignore a repeat.
- No ordering guarantee. Events can arrive late or out of order, so never infer state from arrival order.
- The payload is a signal, not the truth. Re-read the resource before acting on anything that matters.
- Signed, with the event id and timestamp covered by the signature and a tolerance window against replay.
- Answer quickly and do the work afterwards. A slow receiver looks like a failed one and will be retried.
No event names are published here yet. Publishing a catalogue before the emitter exists would be inventing a contract, and the first integration built against it would be built against nothing.