Start with the documentation.
Find the API overview and the guidance needed to understand access, endpoints and permissions.
API & integrations
Your fleet data. Part of your workflow.
Use fleet information where your team already works. Explore documented endpoints, understand permissions and plan an integration around a real operational need.
THE CONNECTION LAYER
GPS devicesAitrackYour systems
Fleet information, connected to the tools your team uses.
Current integration options from the Aitrack documentation. API and webhooks are add-ons.
BUILT FOR THE EVERYDAY
The details that make a difference.
Bring systems together.
Plan how GPS information and fleet events can support the tools and workflows your business uses.
Define access clearly.
Discuss the required scope, usage limits and configuration before enabling an integration.
A FIRST REQUEST
Start with the devices
in your workspace.
Use your server-side environment variable for the API key. The reference explains permissions, response formats and limits.
Read authentication guidancecURL · API v2SERVER SIDE
curl https://api.aitrack.it/api/v2/devices \
-H "X-API-Key: $AITRACK_API_KEY"A documented request example. It is not executed by this page.
A DOCUMENTED FOUNDATION
Read the data. Connect the events.
The stable v2 API exposes fleet information for your business systems. Webhooks bring events to an endpoint, while the v3 beta extends the API with geofence management.
- 01
Plan the integration
Identify the devices, positions, history or events your system needs.
- 02
Configure access
Create an API key with the appropriate permissions and keep it on your server.
- 03
Build with the reference
Use the authentication, errors, delivery and versioning guides to implement and maintain your connection.
Which API version should I start with?
API v2 is stable. API v3 is in beta and adds area/geofence capabilities alongside v2. Consult the versioning and migration guides before choosing.
Are API keys used in browser code?
No. Keep your API key on your server. The documentation explains X-API-Key authentication and permission scopes.
Can the public v2 API send vehicle commands?
The documented public v2 API does not expose command sending. These actions remain internal to the application.
Are API and webhook access included automatically?
They are available as additional components. Confirm access, limits and requirements for your configuration.