Vortex talks to the rest of your operation
Everything the platform does is available through the API. What you do not query gets pushed by webhook the moment it happens.
An API the platform itself uses
It is not a layer bolted on later to tick a commercial box: the Vortex interface consumes the same services we expose to you, with the same validation and the same permissions. If something can be done from a screen, it can be done from the API.
- Token authentication with permission scoping
- Resources for assets, positions, events, geofences, orders and users
- Cursor pagination for large histories
- Usage limits visible in the panel, no surprises
- Interactive documentation with runnable examples
- Sandbox with simulated data
- Call log for debugging integrations
- Versioning with an announced deprecation policy
Per-event webhooks
When you need to react right away, polling every minute does not cut it. Vortex sends the event to your endpoint as soon as it happens, with retry and a persistent queue if your server does not answer.
- Geofence entry and exit
- Speeding and aggressive driving
- Panic button and security alerts
- Fuel refill and drain
- Trip start and end
- Delivery completed or failed
- Temperature excursion
- Device not reporting
Ready-made connectors
For the most common systems no custom development is needed.
ERP and billing
Sync assets, contracts and usage so you bill without typing anything twice.
WMS and TMS
Transport orders, delivery states and evidence into your logistics system.
Payment gateways
Cash on delivery and end-customer subscription collection.
Messaging and email
Notifications through the channels your operation already uses.
BI tools
Scheduled export or direct access for your corporate dashboards.
Corporate identity
Single sign-on with SAML and OAuth against your directory.
Need a specific integration?
Tell us which system you have to talk to and we review what it takes.