ORN Developers
Build on the ORN API
The ORN API is the structured journey infrastructure the network runs on: 61 priced operations across 6 live capabilities — journeys, checkpoints, safety, route intelligence, ORION analysis and passenger insight — over HTTPS as JSON. Authenticate with a bearer key, fund your API wallet, and every call is metered and on the record.
Start here
Work through the path in order. Each step links to the page that does the work.
- Read the introductionWhat the ORN API is, what you need, and how access works.
- Create your application and credentialsDeveloper Console → applications, environments and API keys.
- Authenticate your requestsBearer keys, environments and how scopes are enforced.
- Make your first requestRead one journey record with a single GET call.
- Create a journeyPOST create_journey — draft state, seeded checkpoints.
- Monitor the journeyStatus, monitoring state, timeline and boarding summaries.
- Use safety and checkpointsCheckpoint observations, safety events and assessments.
- Use ORION intelligenceGraduated analysis operations over journey signals.
- Handle webhook eventsReceive journey.created and other delivery events.
Your first request
Read one of your journey records by id. Replace the bearer key and the journey id with your own values — the key is shown once when you create a credential.
curl "https://www.orangeridesnetwork.org/api/v1/journeys/get_journey?journey_id=YOUR_JOURNEY_ID" \
-H "Authorization: Bearer orn_live_YOUR_KEY"GET /api/v1/journeys/get_journey — requires the journeys:read scope. Errors and the response shape are on the Journeys reference.
Do something specific
API reference
Every capability with its priced operations: parameters, scopes, pricing, real response examples and errors.