A
Definition
A set of protocols that allows different software applications to communicate with each other. in NEMT, it allows a Transport Provider's software to "talk" directly to a Broker's software to exchange trip data without manual entry.
Overview
Why it Matters
APIs automate the intake of trips. Instead of a dispatcher manually typing 500 trips from a fax, the API pulls them instantly, reducing human error and labor costs.
How it Works
The Broker’s server sends a "request" (Trip Offer) to the Provider’s API endpoint. The Provider’s system accepts it and sends back a "response" (Confirmation).
Code Comparison
Comparison: API vs. EDI
API is real-time (Trip appears instantly). EDI (Electronic Data Interchange) is usually batch-based (A file with yesterday's trips is uploaded once a day).
Common Questions
- Downtime: If the API link goes down, trips stop flowing.
- Data Mapping: If the Broker sends "Wheelchair" but the Provider's API maps it to "Ambulatory," errors occur systematically.
- Implement "Webhooks" to get instant updates on trip cancellations.
- Always have a manual CSV import backup process in case the API fails.
Sources
IBM - What is an API?