API Reference

With the TMS add-on, another system of yours (a BI tool, an accounting program, a visibility platform) can read your organization's TMS orders, contractors, vehicles and invoices through the TMS API, and your own telematics system can send vehicle positions. In the app's words: "A key lets another system read TMS data, for example orders for reports, or send vehicle positions from its telematics. Besides those positions it changes nothing."

Everything else in Quanty is used through the app at app.quanty.ai. The app's own private API is not offered for integration: it needs a signed-in session and changes without notice.

Before you start

• The organization has the TMS add-on and a paid plan. Without the add-on every request is refused with addon_required; while the plan is unpaid, with payment_required.
• Only an organization admin creates and revokes API keys, in TMS settings, API and webhooks.
• The system that calls the API needs the key, the address of your Quanty API (shown in the key dialog's example) and this page.

API keys

1. Open TMS settings, API and webhooks and click Create key under API keys.
2. Fill in the dialog and click Create key.
3. The key is shown once, with Copy and Example: the first 50 orders (Copy example): "We show this key only once. The list keeps only its beginning; if it is lost, revoke it and create a new one."
4. Paste the key into the system that will use it and click Done.

The list of keys shows Name, Access, Created, Last used ("not yet" until the first request) and Status: Active or Revoked (with who revoked it). Revoke in a key's menu stops it at once: "Systems that use it lose access at once. This cannot be undone."

Reading data

Use the address from the key dialog's example and send the key as a bearer token:

GET /api/v1/ext/tms/orders?limit=50
Authorization: Bearer qk_…

Query parameters

Pages and polling

The answer is one page, oldest change first:

{
  "items": [ { "id": "…", "number": "…", "updated_at": "…" } ],
  "next_cursor": "…"
}

1. Read the first page, with updated_since if you only want recent changes.
2. While next_cursor is not null, read again with cursor set to it (keep the same updated_since).
3. To poll for changes later, start the next run with updated_since a few minutes before the time of your last run.

Rows that changed in the last 10 seconds are not served yet; they come on the next read, which is why a poll goes back a few minutes. Rows with the same updated_at are never skipped or repeated across pages. Deleted rows are left out; cancelled ones keep their status. Answers are never cached.

Fields

Each row has id, created_at and updated_at, and the fields of the matching table in TMS data (see Tables in Quanty). Money and other decimals come as strings ("1234.50"), whole numbers as numbers, dates as YYYY-MM-DD (the day in Polish time), moments in UTC, and choices as codes. A value that is not set is null.

orders

contractors

vehicles

invoices

No internal notes, files, people's ids or coordinates are served. Records that come from Marcos TMS are included like any other.

Errors

A refusal carries a code and a sentence (error_code, message), never anything of the key.

Limits

A valid key is never slowed down by other people's wrong keys.

Sending vehicle positions

For a telematics Quanty does not read itself, your own system can send the positions. The walkthrough, with every field, how vehicles are matched and all the answers, is on Your own system (API). In short:

1. An admin connects Your own system (API) under Telematics: "Nothing to fill in here." The connection shows Receiving: Through the API, Last data, and How to send data with the address, the key it needs and an example request.
2. Make an API key with Telematics: sending.
3. Your system sends the positions:

POST /api/v1/ext/tms/telematics/positions
Authorization: Bearer qk_…
Content-Type: application/json

{
  "items": [
    {
      "vehicle": { "plate": "PO 1AB12" },
      "at": "2026-11-01T10:00:00Z",
      "lat": 52.40,
      "lng": 16.92,
      "speed_kmh": 82,
      "heading": 270,
      "odometer_km": 423434.5,
      "fuel_pct": 61,
      "fuel_l": 410,
      "driver": { "id": "D-17", "name": "Jan Kowalski" },
      "trailer": { "plate": "PO 9TR" }
    }
  ]
}

• vehicle names the vehicle by its Quanty id, its vin or its plate. A vehicle with no telematics yet is linked on its first position; one that takes its positions from another telematics connection is refused for that item.
• at is an ISO moment (without an offset it is read as UTC) or Unix seconds; a time more than 15 minutes ahead of Quanty's clock is refused, so check the sender's clock. lat and lng are required; the rest is optional. The driver's name is personal data, as with any telematics.
• A field an item leaves out keeps the vehicle's last value (fuel, driver), and null clears it. The vehicle's odometer only goes up, so send a real reading. An optional value that is not a reading (a speed of -1, an odometer of 0, a fuel of "n/a") is left out and listed under ignored; the position still counts.

The answer is 200 when at least one item was stored:

{
  "accepted": 1,
  "positions_added": 1,
  "older_than_stored": 0,
  "vehicles_linked": 0,
  "rejected": [ { "index": 3, "status": 404, "error_code": "…", "message": "…" } ],
  "ignored": [ { "index": 0, "field": "speed_kmh" } ]
}

Each item is answered on its own: a refused item is listed under rejected with its index, and the others are stored. The same body sent twice is stored once, and a report older than the vehicle's newest one is added to its trail without moving the vehicle back.

A whole request is refused with:

Other ways to move data

• Google Sheets: import rows from a Google spreadsheet on a schedule, with a key column against duplicates, or export a table the other way.
• Export: any table exports to CSV, Excel or PDF from More actions in the grid (see Projects, tables and views), and the TMS lists and reports have their own export.
• Automations (beta): turn e-mails, WhatsApp messages and KSeF invoices into records of a table, and act on new and changed records.
• Share links: dashboards and presentations can be shared read-only by link (see Dashboards and Presentations).

Questions about the API: support@quanty.ai.