The August release opens up Attire's data programmatically: a new REST API reads your fleet and completed reports into your own systems, and OpenAPI documentation is included in every subscription at no extra cost.
Attire
For all customers   August 2026

REST API and API documentation — now part of every subscription

Your data is yours — now machine-readable too. Every Attire subscription includes an open REST API and API documentation at no extra cost and with no enterprise gate. Read your fleet and reports into your TMS, BI tool or your own intranet. In this letter we cover what the API can do and how to get started.

The API

Fleet and report data in your own systems

The API is plain HTTPS + JSON traffic protected by a single API key (Authorization: Bearer), so it works with any programming language — and with low-code tools such as Power Automate, Zapier or n8n.

There is nothing to order separately: the API is part of every plan. You create the API key yourself in the app's Interfaces view, and it works immediately.

• Included in Pro, Business and Enterprise plans
• Plain HTTPS + JSON calls — any language or tool
• Self-service key, rotate it at any time

New

Completed reports straight from the API

The new report read endpoint returns your licence’s completed reports — both your own and the ones your workshop has shared with you. For every report you see, among other things, the vehicle, report type, modules and completion time.

A timestamp filter fetches only the reports changed since your previous sync, so keeping your own system up to date stays lightweight. And as always in Attire: reading shared reports is free of charge.

• Your own and workshop-shared completed reports
• Filter by vehicle, registration number or timestamp
• Reading shared reports is always free of charge

Documentation

OpenAPI 3 documentation for signed-in users

Once signed in, you have interactive API documentation (Swagger UI) where you can try calls right in the browser — during the free trial too.

From the downloadable OpenAPI 3 schema you can generate a ready-made client library for example for C#, Java, Python or TypeScript. Calls are protected with HTTPS and usage is rate-limited to prevent abuse.

Use cases

TMS sync, BI reporting and your own archive

Keep your vehicle list up to date in your transport management system and attach the workshop’s service reports to the vehicle’s records automatically. Or export service and inspection data to Power BI and combine it with the rest of your business data.

The API is also insurance for the ownership of your data: you can read it out at any time. The information is your property, not a hostage.

• TMS / fleet management: fleet and reports up to date
• BI: service data as part of your reporting
• Your own archive: your data out with one call

For workshops

A selling point for workshop customer work

When your transport customer asks about integrations, the answer is now easy: a customer on Attire can read the reports you make for them straight into their own systems — at no extra cost, with no project work. It is a differentiator many competing systems do not offer.

Broader integrations (for example Automaster, Netvisor or SSO) are built for Enterprise customers as integration work — tell us what you need and we will work it out together.

Included in your subscription

Explore the API

The API is already available to you. See an example call and the three-step getting-started guide on the API page — or sign in and open the API documentation.

Read more about the API