Integrations
Your outsourced fleet on one screen, with no mirror accounts.
More than 60 GPS and telematics platforms with a built-in connector, and any other that can send data through an API. No hardware and no integration fee.
Your whole outsourced fleet on one screen, no mirror accounts
The GPS your carriers already have, connected to Aliado
- Before
- 7+ One portal and one password per carrier; your operator jumps between tabs
- With Aliado
- 1 One control tower, no hardware and no integration fee
Platforms with a built-in connector; no commercial relationship implied
Global platforms
Mexico and Latin America
Don't see your provider? We'll integrate it; what usually takes longest is the provider's reply.
How the signal comes in
- PollingAliado queries the provider’s platform using the carrier’s access
- API pushThe provider or your system sends positions to Aliado with its own key
- Data streamsKafka and AWS Kinesis for high volumes
- Direct deviceDevices that report to Aliado with no intermediate platform
API for your IT team
- PositionsSend GPS readings one at a time, in batches or from a phone
- Trips from your TMSCreate or replace a planned trip with stops, units and drivers
- Events and alertsPush trip events and third-party alerts
- ResourcesCreate, read, update and delete units, drivers and addresses
- Trips and appointmentsList, create, start and end trips; create and respond to access appointments
REST API with an OpenAPI contract. Documentation and a sandbox are provided when the integration starts.
For your IT team
Frequently asked questions
How does the API authenticate?
With one key per organization in the authorization header. The key defines the organization and the permitted capabilities.
Does the key give access to everything?
No. Each family of operations requires its own capability; a key without it is rejected.
Is there a test environment?
Yes. Development and production are separate, with different credentials.
What do you need from our GPS?
The API user or token for your platform, or for your provider to send us data by API. No hardware is installed.
Can stored passwords be viewed?
No. Stored secrets are never displayed, and a generated credential is shown only once.
Who owns the data?
Credentials and units belong to your organization. When a partnership ends, the two organizations stop seeing each other.
How do I control who sees what?
With roles (Administrator, Operator, Guard, Installer), permissions by module and tags by resource.
Can a token be revoked?
Yes. It stops working on the platform and for data intake.
Corporate single sign-on?
Email and password, or Google, Microsoft or Apple.