Guarantor software in Álava, Bizkaia and Gipuzkoa

TicketBAI software for Bizkaia, via API

The Verifacti TicketBAI API connects your invoicing software with the Bizkaia Foral Treasury (Batuz): you send each invoice as JSON, instantly get the QR and TicketBAI code, and Verifacti generates, chains and submits the TicketBAI file, which is recorded in the Batuz LROE. Verifacti is TicketBAI guarantor software in Álava, Bizkaia and Gipuzkoa, with the same endpoint for all three territories.

Read the documentationTicketBAI API
Test environment and test NIF included
POST /ticketbai/create
{
  "serie": "A",
  "numero": "234634",
  "fecha_expedicion": "19-11-2026",
  "tipo_operacion": "servicios",
  "importe_total": "242.00",
  …
}
200 OK · instantly
{
  "tbai": "TBAI-B05434202-021224-…",
  "estado": "Pendiente",
  "qr": "iVBORw0KGgoAAAANSUhEUgAA…"
}

How the TicketBAI API works in Bizkaia

  1. 1

    You send the invoice as JSON

    Your software calls the API with the invoice data and the issuing NIF’s API key.

  2. 2

    You get the QR and the TicketBAI code

    Instantly, to print on the invoice.

  3. 3

    Verifacti submits the file to the Bizkaia Foral Treasury (Batuz)

    It generates the file, chains it and records it in the Batuz LROE (form 140 or 240), in the background.

The result reaches you by webhook or by checking the record’s status.

Example: create a TicketBAI invoice for Bizkaia

It is the same endpoint for all three territories: the target treasury comes from the NIF. For individuals (form 140), each invoice carries its activity code in detalle_renta.

Request · cURL
curl -X POST https://api.verifacti.com/ticketbai/create \
  -H "Authorization: Bearer $VERIFACTI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "serie": "A",
    "numero": "234634",
    "fecha_expedicion": "19-11-2026",
    "simplificada": false,
    "nif": "A15022510",
    "nombre": "Empresa de ejemplo SL",
    "direccion": "Calle Mayor 15",
    "cp": "48992",
    "descripcion": "Descripción de la factura",
    "tipo_operacion": "servicios",
    "lineas": [{
      "descripcion": "Línea 1",
      "cantidad": "2",
      "importe_unitario": "100.00",
      "importe_total": "242.00"
    }],
    "desglose_iva": [{
      "base_imponible": "200",
      "tipo_impositivo": "21",
      "cuota_impuesto": "42"
    }],
    "importe_total": "242.00"
  }'
Response · 200
{
  "uuid": "ea6eae92-bac6-48c3-baa4-2bbf6b5ee562",
  "tbai": "TBAI-B05434202-021224-mwUG7NRo2ZNxp-010",
  "estado": "Pendiente",
  "url": "https://…/qrtbai/?id=TBAI-B05434202-021224-…",
  "qr": "iVBORw0KGgoAAAANSUhEUgAA…"
}

What the TicketBAI API includes in Bizkaia

  • Guarantor software in Bizkaia

    Verifacti is guarantor software here and in the other two territories. The software calling the API does not need to join the guarantor software register.

  • Submission to the Batuz LROE

    Every issued invoice is recorded in the LROE: form 140 for self-employed individuals, with the activity code in detalle_renta, and form 240 for entities. Verifacti picks the form from the NIF’s type of person. What the LROE is.

  • Registration and cancellation

    In Bizkaia the API records each issued invoice and its cancellation (/ticketbai/cancel). It does not submit the rest of the LROE (expenses, received invoices…), and Bizkaia does not accept modification or amendment through the API.

  • Validation before sending

    Every invoice is validated before it is sent and any error comes back with a code (code catalogue). By default we also check that the customer’s NIF is identified by the AEAT.

  • No digital certificate

    The taxpayer signs the representation form once, also online.

  • The same endpoint for all three territories

    Each NIF is assigned its treasury when registered; the call to /ticketbai/create is the same in Álava, Bizkaia and Gipuzkoa.

One integration per regulation, on top of the NIF management API

You integrate the NIF management API once: registering, activating and removing NIFs, representation and webhooks. Each regulation then adds its own submission integration, close to the target administration’s API. If a customer is taxed in common territory, they use the Verifactu API with the same NIF management and the same price.

Why Verifacti for TicketBAI in Bizkaia

Built for developers

Public documentation with examples for every call, quick start guide, Postman collections, llms.txt and a free account with a test environment.

Typical integration: one to three developer days

Specialists in Spain

Common and foral territory: Verifactu, TicketBAI and SII with one provider.

Guarantor software in Álava, Bizkaia and Gipuzkoa

Proven reliability

Hundreds of companies and software vendors in production with Verifacti. Data hosted in the EU and an SLA in the terms of use.

AEAT social collaborator

TicketBAI in Bizkaia: dates and official source

In Bizkaia, TicketBAI is part of Batuz together with the LROE, and it has applied to all taxpayers since 1 January 2026.

Batuz in Bizkaia (TicketBAI and LROE): all taxpayersSince 1 Jan 2026
Companies that are not SMEs since 1 January 2024; everyone else in windows on 1 July 2024, 1 January 2025, 1 July 2025 and 1 January 2026.
In force

This is not advice: each taxpayer determines what applies to them with their adviser.

TicketBAI API pricing

From

€14.99

/month per NIF active in production, excl. VAT

See all prices
  • The price per NIF goes down with every tier.
  • Up to 3,000 invoicing records per month per NIF.
  • Online signing of the representation form: €2.90 + VAT.
  • Free test environment and test NIF.
  • Annual plan with a 10% discount, no setup fees.
  • Same price as the Verifactu API.
  • Startup plan for companies under 12 months old, with under €100,000 in revenue and under €200,000 in funding.

Questions about TicketBAI in Bizkaia

More questions about TicketBAI

Is Verifacti TicketBAI guarantor software in Bizkaia?

Yes, and in the other two foral territories too.

Does my software need to register as guarantor software?

No. Verifacti is the guarantor software; your program calls the API.

Which LROE form does it use, 140 or 240?

Form 140 for self-employed individuals and form 240 for entities. Verifacti picks it from the NIF.

Do I need a digital certificate?

No. Verifacti is an AEAT social collaborator and submits with its own certificate once the taxpayer signs the representation form, the same one for the AEAT and the foral treasuries. It can be signed online, without a certificate.

How much does it cost?

The same as the Verifactu API, per NIF active in production. See pricing.

Start integrating today

Try it for free with the test environment.

Test environment and test NIF includedSee pricing