Introduction
Bilteo is an electronic invoicing platform with Veri*Factu. It offers two different products, depending on who issues the invoice:
- Bilteo Public API — Bilteo is your invoicing system: you create the invoice; Bilteo numbers it, calculates taxes, generates the document (PDF/Facturae), and registers it with Veri*Factu.
- Verifactu Direct API — Bilteo is your Veri*Factu gateway: your software has already issued the invoice; Bilteo only registers it with Veri*Factu and submits it to the Spanish Tax Agency (AEAT).
These are not separate APIs. Both use the same REST API (/api/v1), the same scopes through API keys or OAuth2, and the same Veri*Factu chain. The model and purpose are what differ. You can use either product or both.
Which one do I need?
Choose the Bilteo Public API if you want Bilteo to issue and number invoices. Choose Verifactu Direct API if your software already issues them and you only need to register them with Veri*Factu.
Concepts
- Tenant — your company or taxpayer within Bilteo. Each API key or OAuth2 connection operates on one tenant only.
- Veri*Factu record — the invoice record, either creation or cancellation, that Bilteo fingerprints, chains, and submits to the AEAT. Both products generate it.
- Series / Invoice — concepts used by the Public API: an invoice starts as a draft and receives its number from a sequential series when issued. With Verifactu Direct API, you provide the series and number.
The API in one sentence
REST over HTTPS, JSON, scoped API-key or OAuth2 authentication, and an OpenAPI 3.1 specification available in the API reference.
Base URL: https://api.test.bilteo.com/api/v1Example host
Replace https://api.test.bilteo.com with the host for your environment. Test (sandbox) tenants submit to the AEAT test services; live tenants submit to production.
Where to start
- Bilteo Public API (issue through Bilteo) → Getting started.
- Verifactu Direct API (register an already-issued invoice) → Verifactu Direct API.
- Full endpoint contract → API reference.