Developers
This section is for technical teams that want to connect their own systems or tools to RushHour: an ERP or warehouse system that creates orders, a reporting job that pulls invoices, or an AI assistant that looks things up for your dispatchers.
What you can build with today
The RushHour API is the same web service that the Company Portal, the Customer Portal and the driver app use. Everything your team does in the Company Portal goes through it, so your own software can do the same things — with the same permissions.
- It is a REST API over HTTPS that sends and receives JSON.
- It lives at
https://api.rushhourapp.com/api/v1. - Requests are made on behalf of a RushHour user, and that user's roles and permissions decide what each request may see and do.
- An integration authenticates with an API token that a company admin creates in the Company Portal, or by signing in as a dedicated Company Portal user.
What's on the way
An MCP server for AI assistants — a way for AI assistants to work with your RushHour data on behalf of a RushHour user. It is not available yet, and its details have not been published.
Card payments API — endpoints for charging and authorizing customer cards through Cardknox or Stripe, refunds and payment requests. See Card payments API.
Where to start
| Page | Read it to learn |
|---|---|
| API overview | The base URL, versioning, request format, the response envelope, status codes and error codes. |
| Authentication | How requests are authenticated, how to get a session token by signing in, and how long it stays valid. |
| API tokens | Authenticating an integration without a person's password. |
| Pagination and filtering | Paging through lists, searching, sorting and filtering. |
| Dates and time zones | How timestamps are sent and returned, and how to query by day. |
| Rate limits | What happens when you send too many requests, and how to retry. |
| Webhooks | Whether RushHour can notify your systems about changes. |
| MCP server for AI assistants | Coming soon — connecting AI assistants to RushHour. |
| Card payments API | Coming soon — charging customer cards, refunds and payment requests. |
A first request in three steps
- Get a token: ask a company admin to create an API token, or sign in with a Company Portal user — see Authentication.
- Send the token in the
Authorizationheader of every request. - Read the
success,dataanderrorsfields of the JSON response — see API overview.
curl "https://api.rushhourapp.com/api/v1/Customers?itemsPerPage=5" \
-H "Authorization: Bearer YOUR_TOKEN"
API reference
The API reference covers the individual endpoints available to integrators. Use it together with the pages above: their rules for authentication, responses, paging and dates apply to every endpoint.
Good practice for every integration
- Use a dedicated user. Create a separate Company Portal user for each integration and give it only the roles it needs. Its actions then show up under its own name, and you can disable it without affecting anyone else.
- Keep credentials on your server. Call the API from a backend you control. Never put a password or token in a web page, a mobile app, a spreadsheet shared with others, or a chat message.
- Plan for failure. Handle error responses, retry only when it is safe to do so, and back off when the API asks you to slow down.