tray-notas-fiscais

To create an NF-e electronic invoice for a Tray order, send a POST request to the /orders/:order_id/invoices endpoint. You must wrap your payload in an Invoice object and include a valid 44-digit access key, number, series, issue_date, and a public DANFE link.

The required format for an NF-e access key in Tray API integrations is a strict 44-digit numerical string. Validating this 44-digit key format before submitting your POST or PUT request ensures the electronic invoice payload is accepted without errors.

Yes, you can list and filter Tray electronic invoices in bulk for ERP integration using the GET /invoices endpoint. This endpoint supports pagination and filtering by order, invoice number, and dates to retrieve billing records at scale.

To query a specific Tray order and find its associated fiscal documents, call the GET /orders/:order_id/invoices endpoint. This retrieves all NF-e electronic invoices linked to that particular order for reconciliation.

Yes, the Tray NF-e API supports updating existing electronic invoice records using the PUT /invoices/:id endpoint. You can modify common fiscal fields like number, series, issue_date, key, cfop, and total_amount after creation.

To manage Tray invoices through API endpoints, you need an access_token set as a query authentication parameter. This token authorizes all requests to list, query, create, and update NF-e records.