Integrations and API

Fits into the systems you already run

Routyn is API-first. Orders come in from your systems, optimized trips go out to your drivers and carriers, and results flow back to your reporting.

Ways to connect

Real time or in batches, your choice

REST API

Send orders, fleet and driver data in near real time, and read planned trips back. Public Swagger documentation.

File exchange

XML or CSV files over SFTP or a shared folder, for WMS, TMS and ERP systems that work in batches.

Telematics

Native connections to several vehicle tracking providers.

Other driver apps

Already run a mobile app for drivers? Send it trips and receive execution events through the API.

BI and reporting

Export plans, costs and results to Power BI and other BI tools.

Single sign-on

Microsoft Entra ID sign-in with role-based access.

Telematics partners

Works with the trackers in your vehicles

  • Frotcom
  • Cartrack
  • TomTom

See all our partners →

Built to last

Integrations that survive upgrades

Every customer runs the same product version and the API is kept stable, so your integrations keep working when Routyn improves.

  • Stable, versioned REST API
  • Rollouts in new countries reuse the same integrations
  • Full data export at any time, at no cost
FAQ

Frequently asked questions

More questions? Talk to our team.

Is there public API documentation?

Yes. The REST API is documented in Swagger and you can browse it before you sign anything.

Our systems work in batches. Is that a problem?

No. Routyn exchanges XML or CSV files over SFTP or a shared folder, loading them through the same API.

Will upgrades break our integration?

The API is stable and breaking changes are rare. Everyone runs the same product version, and upgrades follow change management.

Can we get all our data out?

Yes, at any time, through the API, including when you leave, at no cost.

Let Routyn lead the way

Handling delivery routes doesn’t have to be hard. Choose the smarter way, the Routyn way.