Your Operation. Connected.
Registration, settlements and tax documents. Connect FleetPay workflows to the software your operation already uses.
Start Integrating ↗Start in the Sandbox
Each environment has its own credentials. Create yours under Settings → API Integration and enable the scopes you need.
https://api.fleetpay.site/v1https://api.fleetpay.tech/v1Check Fiscal Access
Read-only example: no document issuance or payment. Requires the fiscal scope.
curl https://api.fleetpay.site/v1/fiscal/status \
--header "Authorization: Bearer $FLEETPAY_API_KEY" \
--header "Accept: application/json"Keep credentials on the server. Never include keys in browser code.
Explicit Permissions
Every credential starts with no access. Scopes enabled in the dashboard determine which operations it can perform.
fiscal
Tax documents and configuration. Available to carriers only.
operacao
Release and payment of settlement instalments. These operations move money.
cadastros
Invitations, contracted driver lookup and Pix key verification.
consultas
RNTRC registry queries.
API Key or OAuth2
Both methods use Authorization: Bearer. Static keys start with fp_hml_ or fp_prd_, depending on the environment. OAuth2 uses client_credentials at POST /oauth/token, outside /v1. Tokens expire after one hour; request a new token when needed.
Authorization Responses
Credentials used in the wrong environment receive 401. Operations outside enabled scopes receive 403 with error.code: escopo_nao_habilitado.
Simulation and Regulatory Effect
The current contract identifies CIOT operations and ANTT queries as simulated in the sandbox, with no regulatory effect. In production, these operations reject execution while the corresponding provider is unavailable. CT-e and MDF-e use a fiscal sandbox integration; check the environment field before treating an issuance as final.
The Next Integration Path
Explore implemented MCP queries and their limits. External integration depends on assessment, enablement and sandbox validation.
Explore MCP ↗