Connect the software you already run to Bambi.
A REST API and real-time webhooks for NEMT trips. Your CRM, intake tools and own apps stay in step with dispatch, so nobody keys the same trip into two screens.
Building for NEMT providers? Partner with us →
Your systems and Bambi, finally talking.
A trip created in your software lands on the Bambi dispatch board. Every status change comes back to you the moment it happens.
Book trips from your own systems
Create, update and cancel trips from the software you already use. They land in Bambi ready for Run Bambi Run.
POST /organizations/{id}/trips/Know the moment anything changes
Signed webhooks for 21 trip events: accepted, assigned, en route, at pickup, completed, canceled and more.
trip.en_route → your endpointKeep your records in step
Driver, vehicle and timestamps come back on every trip, so billing and reporting never wait on a phone call.
GET /trips/{id}/events/trip events, signed and delivered the moment they happen
for bursts, with 5,000 an hour sustained
notice before any breaking change, old and new side by side
per active vehicle a month, on top of your Bambi plan
What you can build this month
Every idea below runs on trips, payers, drivers, vehicles and webhooks, the same endpoints in the docs today.
CRM
Facility relationships in your CRM
See every facility, clinic and broker you serve inside the CRM you sell from: rides booked, completed, canceled and revenue. Spot the facility whose rides are slipping before it walks.
Will-call
Will-call, from the front desk
When a dialysis center or discharge desk says the passenger is ready, the will-call trip activates in Bambi.
Rider updates
"Your ride is on the way," from your own app
Send your own texts, or update a facility's portal, the moment a driver heads out.
Intake
Trips straight from your intake
Your phone intake, CRM or booking app creates the trip. Bambi has it before anyone retypes it.
Reporting
Trip data wherever you work
Completed trips and prices flow into Google Sheets, Power BI, a data warehouse or any custom app.
Live board
Your own live board
Put today's trips on the office TV or a control-room screen, laid out the way your team works.
Alerts
Heads up when plans change
Cancellations and rejections land in Slack, Teams or a text, so nobody finds out at pickup.
Roster
One roster, everywhere
Driver and vehicle records stay in step with HR and fleet maintenance.
No developer? Start with no-code.
Point Bambi webhooks at Zapier, Make or n8n and build simple automations without writing code.
Brokers and plans
Brokers and health plans
Place trips with the Bambi providers you already work with, and get live status back.
PACE
PACE programs
Send contracted trips and track them next to your in-house runs, so every participant's ride is in one view.
Facilities
Hospitals, senior living, dialysis and home health
Book and track rides from inside the systems your care teams already use, including standing orders for recurring rides.
Caregivers
Family and caregiver apps
Let a family member see a parent's ride on their calendar and get a text when the driver is on the way home.
Telematics
Fleet and telematics tools
Read trips, drivers and vehicles to line them up with your own vehicle data.
Partner terms
Partner terms are set together
Tell us who you serve and what you want to build. We'll scope access and terms with you.
You might not need this. Broker integrations with MTM, Modivcare, Verida and more are already included in your Bambi plan, and so is a trip request form for your website. The Developer Platform is for writing your own software alongside Bambi. See every included integration
How it works
From asking for access to live trips flowing both ways, in four steps.
Step 1
Ask for access
Owners and admins request it from Developer Platform in Bambi's top-right menu. Tell us what you want to build.
Step 2
We set you up
Bambi issues separate staging and production credentials and delivers them securely.
Step 3
Build against staging
OAuth2 client credentials, REST endpoints and a full OpenAPI schema your AI coding tools can read.
Step 4
Go live
Add webhook endpoints, watch delivery history and resend anything that failed, all from the same page in Bambi.
Built to be built on
docs.hibambi.com, plus an llms.txt and an OpenAPI schema.
Before any breaking change, with old and new side by side where possible.
A secret you can rotate, test deliveries, 90 days of history and one-click resend.
Webhook payloads carry IDs, statuses and timestamps only.
120 requests a minute for bursts, 5,000 an hour sustained.
Separate credentials, so you never test on live trips.
# Get a token, then create a trip
Pricing
On top of your Bambi plan. Partners sending trips to Bambi providers: terms set together.
Pick your way in
Three kinds of teams build on Bambi. Here's the fastest path for each.
Already on Bambi
Turn it on from inside Bambi
Owners and admins ask for access from Developer Platform in the top-right menu. We already know who you are, so it's one question.
Request access in Bambi →Not on Bambi yet
Start with the $69 product the API runs on
Book a short demo built around your routes and brokers. Add the Developer Platform once you're running.
Book a demo →Partners
Brokers, plans, PACE, facilities and vendors
Send trips to the Bambi providers you already work with. Tell us what you're building and we'll set terms together.
Tell us what you're building →Developer Platform questions
Pricing, access, partners and what we promise not to break.
Is the Developer Platform included in the $69?
No. The $69 covers everything you need to run your operation, including broker integrations. The Developer Platform is a separate product for writing your own software alongside Bambi, or taking Bambi trip data into your other applications, at $30 per active vehicle a month.
Who can request access?
Account owners and admins, from Developer Platform in Bambi's top-right menu. Dispatchers can see the page and are asked to contact an admin.
Do I need a developer?
Yes, or a software vendor who builds it for you. Simple automations can run through no-code tools like Zapier, Make or n8n. If you don't write code, the integrations already in your Bambi plan probably cover what you need.
Can brokers, health plans and PACE programs use it?
Yes. They connect as partners that send trips to the Bambi providers they work with. Tell us what you're building and we'll set terms together.
Can hospitals and care teams book rides from their own systems?
Yes. A hospital, health system or care platform can connect its own software to the API and book and track rides with the Bambi providers it works with. Bambi doesn't ship a ready-made connector for any specific EHR. The connection is built on the API by the facility or its software vendor.
Will you break my integration?
We give 90 days notice before any breaking change and run old and new side by side where we can. Security and legal fixes are the only exception.
Where are the docs?
At docs.hibambi.com, with a full API reference, webhook guide, OpenAPI schema and llms.txt.
Ready to Run with Bambi?
