Rydmate API

Transport and logistics infrastructure you can build on.

The same operation Rydmate Cloud runs, over HTTPS. Create trips and tickets, book shipments, follow vehicles and hear about every event, from your own product or a partner integration. Start in a free sandbox.

Book a demoRead the documentation
Your first request
curl https://api.rydmate.com/api/v1/vehicles \
  -H "Authorization: Bearer ryd_test_your_key"

{
  "data": [
    { "id": "…", "registration_number": "SBX-101AA", "seat_capacity": 14, "status": "ACTIVE" },
    { "id": "…", "registration_number": "SBX-202AA", "seat_capacity": 14, "status": "ACTIVE" }
  ]
}

Resources

Everything the dashboard manages, as an API

Versioned under /api/v1. Every resource is scoped to the business the key belongs to; another business's records do not exist as far as your key can tell.

Vehicles and drivers
The fleet and the people who drive it, with documents and assignments.
Routes and trips
Priced routes, scheduled departures, seat maps and manifests.
Tickets
Sell a seat, hold it, confirm it, cancel it. Every ticket carries proof.
Shipments
Book an order, dispatch a shipment, follow it to proof of delivery.
Tracking and telemetry
Live positions for every vehicle, and a feed for any GPS device that posts JSON.
Transactions and receipts
What was collected, by which method, with the receipt for it.
Reports
The fourteen operational reports, as data.
Webhooks
Signed deliveries the moment a trip, ticket, shipment, payment or position changes.

How it is built

Infrastructure, not a side door

One operating record

A ticket created by your product is the ticket the owner sees on the dashboard, the driver scans, and the report counts. There is no second system to keep in sync.

  • Same permissions, same rules
  • Same money rules: integer kobo, server-priced
  • Cross-tenant reads return not found

Built for real networks

Every write that matters accepts an Idempotency-Key, so a retry over a flaky connection never sells a seat twice. Rate limits are stated in headers, not discovered.

  • Idempotency on creates
  • X-RateLimit headers on every response
  • Consistent error bodies with a request id

Safe by default

Keys carry scopes and nothing else: no key can manage the business, its people or its plan. Secrets are shown once and stored hashed. Webhooks are signed and replay-protected.

  • Scoped keys, rotation and revocation
  • HMAC-SHA256 signatures
  • Audit trail on every key action

Getting started

From sign-up to first request in minutes

  1. Create an account

    Sign up as you would to run a business. The account is free and needs no card.

  2. Mint a test key

    Under Developers, create a key with the scopes you need. Your sandbox is provisioned the same moment, seeded with vehicles, drivers, routes and a departure.

  3. Make the first request

    List the sandbox's vehicles. Then create a trip, sell a ticket, book a shipment. Everything you create appears on the sandbox dashboard.

  4. Go live

    Choose a Rydmate API plan, or use the integration API included with a Cloud Scale plan. Mint a live key and point your integration at the real business.

Book a demoAPI pricing