API Issuing

API invoice creation is used when you need to issue invoices programmatically by integrating Brinta with your system or ERP.

This option is ideal when you:

1. Want to automate invoice issuance
2. Issue invoices in real time from your own system
3. Work with large or continuous invoice volumes
4. Need a scalable and fully integrated solution

With API invoice creation, you can:

1. Send invoice data directly to Brinta via API
2. Issue invoices without using the dashboard
3. Handle multiple document types programmatically
4. Receive real-time responses and validation results

This method follows the same validation rules as manual and bulk invoicing, including country-specific electronic invoicing requirements.

How it works

All invoice creation goes through a single endpoint:

POST https://api.brinta.com/invoices

The payload structure is the same across all countries and document types. What changes is which fields are required depending on the country and document type you're issuing.

The general flow is:

1. Authenticate — include your API key in the request header.
2. Build the payload — set invoice_type, document_type, and the fields required for your country.
3. Send the request — Brinta validates, stamps, and returns the signed document.
4. Handle the response — check the status and store the invoice ID and fiscal UUID returned.

Payload structure

Every request shares the same root structure:

payment_method structure

payment_method accepts either a single object (as before) or an array of objects with the same shape, to split an invoice's payment across multiple methods (e.g. part bank transfer, part credit card).

Example — single payment method (unchanged):

"payment_method": {
  "type": "credit card",
  "name": "Visa",
  "bin": 400344,
  "last4": 5563
}

Example — multiple payment methods:

"payment_method": [
  {
    "name": "bank account",
    "type": "bank transfer",
    "code": "03",
    "amount": 1000,
    "due_date": "2026-08-20",
    "installments": 1,
    "bank_account_sender": {
      "bank_name": "aaa",
      "account_number": "123456"
    }
  },
  {
    "name": "VISA",
    "type": "credit card",
    "code": "03",
    "amount": 2000,
    "due_date": "2026-08-20",
    "installments": 2
  }
]

Authentication

Include your API key in every request:

curl --request POST \
  --url https://api.brinta.com/invoices \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{...}'

Document types by country

For a complete list see Invoice Document Types.

Response

A successful request returns 201 with the created invoice object, including:

• id — Brinta invoice UUID
• invoice_key — Fiscal UUID (folio fiscal) stamped by the tax authority
• status — Current invoice status
• xml / pdf — Signed document links (where applicable)

For error codes and status descriptions see Invoice Status Codes and Invoice Errors.

Useful Links

Response

A successful request returns 201 with the created invoice object: id (Brinta UUID), invoice_key (fiscal UUID / folio fiscal), status, and xml/pdf signed document links where applicable.

Credit Notes (all countries)

Credit notes follow the same logic across all countries Brinta supports. A credit note is created by sending invoice_type: "credit" and referencing the original invoice being credited via original_invoice_id or original_invoice_external_id. See Credit Notes for the full field reference, including the multi-company origin_company_id case.

Country specifics