Conventions
The things that are true of every Ryde API call.
| Topic | Convention |
|---|---|
| Transport | HTTPS only. Plain HTTP is refused, never redirected — a redirect would have already leaked the token. |
| Format | JSON request and response bodies, UTF-8. |
| Version | In the path: /v1/… |
| Auth | Authorization: Bearer <access token> |
| Resource ids | Opaque strings. Do not parse them, and do not assume a length or an alphabet — they are not guaranteed stable in shape across products. |
| Timestamps | RFC 3339 with an explicit offset. Appointment times are also returned in the market's local wall clock, because a customer thinks in local time. |
| Money | An amount with an explicit currency code, in the market's own currency. Never assume USD. |
| Location | Decimal lat/lng, plus a human address string where one is known. |
| Request id | X-Ryde-Request-ID on every response. Log it; support needs it. |
Ryde's launch market is the Dominican Republic and prices are quoted in Dominican pesos. Any figure you display to a customer should come from a Ryde response with its currency, never from arithmetic your client performed.