Versioning and changelog

API versions#

The version is in the path: every endpoint today is under /v1. Within /v1, DollarTraq will not make a change that breaks a correct integration. Anything that would is released as /v2, and /v1 keeps working for at least 12 months after /v2 ships, with notice sent to every account.

These changes are not breaking, and can happen within /v1 at any time:

• New endpoints, new optional query parameters, new response headers.
• New fields in a response.
• New values for flags, severity, knockout.reasons[].code and error codes.
• Different wording in message, verdict, detail and other text meant for people.

Write your code to ignore fields it does not know and to handle unfamiliar values, so these changes reach you without work.

Each response carries a DT-Api-Version header naming the release that served it.

Scoring model versions#

The scoring model improves over time: new checks, better thresholds, new data sources. A model update can move a carrier's score and decision without any change to the API, because it is the score itself that changes.

• Every response names its model_version. Store it with each decision.
• Model updates that move many carriers' scores are announced to every account before they take effect.
• The sandbox's test carriers do not change with model updates, so your tests stay stable.

Changelog#

2026-10-15: v1 released#

• GET /v1/dt-score by USDOT or MC number: score, grade, decision, verdict, knockout, reasons, checks, flags, data confidence, model version.
• GET /v1/usage for limits and monthly usage.
• GET /v1/health for status checks.
• Sandbox at https://sandbox-api.dollartraq.com with six test carriers and a simulated outage.
• Scoring model dt-trust-v3.5.