BeeL (beel.es) provides a cloud‑based invoicing platform for Spanish businesses, offering the VeriFactu API that automates invoice creation, submission to the AEAT, and integration with Stripe. The service includes SDKs, CLI tools, sandbox testing, and AI‑assisted agents, supporting multi‑NIF, recurring invoices, and compliance features. Documentation, pricing, and support are publicly available.
beel-es publishes 54 API contracts indexed on the APIs.io network, including Account Companies API, Account Email Domains API, Account Emails API, and 51 more. Tagged areas include invoicing, Spain, API, fintech, and SaaS.
The beel-es catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.
beel-es’ developer surface includes CLI, authentication, sandbox, changelog, API reference, documentation, pricing, and 32 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/beel-es/"><img src="https://apis.io/badge/beel-es/card.svg" alt="beel-es on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
Agentic Commerce Well-Known Document+5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
Consent & Bot Identity+3 pts — common[].type includes AIPREF, ContentSignal, WebBotAuth, or HTTPMessageSignatures
Kin Score — facets with the most composite points still available (weight × headroom):
Access Clarityscores 38.9 — up to +12.2 composite points
The domains an account sends its emails from, addressed by `/v1/accounts/{account_id}/email-domains`. The account in the path is the only source of context, instead of being der...
The sent-email history of an account, addressed by `/v1/accounts/{account_id}/emails` and `/v1/accounts/{account_id}/email-indicators`. The account in the path is the only sourc...
Onboarding managed accounts in bulk from a file, addressed by `/v1/accounts/imports`. The file is declarative and the import is re-runnable: each pass applies only what is missi...
Canonical form of the request logs, addressed by `/v1/accounts/{account_id}/request-logs`. The account in the path authorizes the call; the logs returned are always the requests...
Account provisioning for partners managing multiple accounts and NIFs. The whole onboarding flow — provisioning, claim tokens and usage — works with either API key: the account ...
Outbound webhook subscriptions as a sub-resource of the account itself, addressed by `/v1/accounts/{account_id}/webhooks`. The account in the path is the only source of context ...
The company as a resource of its own, addressed by `/v1/companies/{company_id}`. The NIF in the path is the only source of context: the account that owns it is derived from it.
Switching a company on or off in Test or Live, as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/activations`. The NIF in the path is the only so...
The invoice branding of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/logo` and `/v1/companies/{company_id}/invoice-customization`....
Importing customers into a company, addressed by `/v1/companies/{company_id}/customers/imports`. The origin of the file travels in the body as `source`, so adding an origin neve...
The customers of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/customers`. The NIF in the path is the only source of context: the a...
The invoice custom fields of a company, addressed by `/v1/companies/{company_id}/custom-fields`: labels a company adds to its invoices, such as a store, a project or a cost cent...
The email configuration of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/email-configuration`. It sets the address the invoice emai...
The fiscal summary of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/fiscal-summary`. The NIF in the path is the only source of cont...
Delivery, bulk operations and exports of a NIF's invoices (send, deliveries, batches, exports, PDF archive), under `/v1/companies/{company_id}/invoices/...`. Canonical form of `...
State transitions and scheduling of a NIF's invoices (issue, void, corrective, status, schedule), under `/v1/companies/{company_id}/invoices/{invoice_id}/...`. Canonical form of...
The invoices of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/invoices`. The NIF in the path is the only source of context: the acc...
The payment provider connections of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/payment-connections`. The NIF in the path is the ...
The payment events of a company connection, addressed by `/v1/companies/{company_id}/payment-connections/{connection_id}/events`. The NIF in the path is the only source of conte...
The product/service catalog of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/products`. The NIF in the path is the only source of c...
Converting a NIF's proforma into a fiscal invoice (`POST /v1/companies/{company_id}/invoices/{invoice_id}/convert-to-invoice`). The rest of the proforma workflow happens through...
The recurring invoice templates of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/recurring-invoices`. The NIF in the path is the on...
The AEAT fiscal representation of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/representation`. The NIF in the path is the only so...
The invoice series of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/series`. The NIF in the path is the only source of context. It ...
The tax configuration of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/tax-configuration`. The NIF in the path is the only source o...
The VeriFactu configuration of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/verifactu-configuration`. The NIF in the path is the o...
The variables the email templates accept, addressed by `/v1/email-template-variables`. The catalogue is the same for every credential and takes no identifier.
Who am I (`GET /v1/me`): the authenticated principal — credential type, environment it operates on and the permissions it holds — so a client can adapt what it offers instead of...
Member invitations — invite people to the account and revoke pending invites (multi-NIF). Like members, invitations are **shared between Test and Live**: accepting one grants re...
Account member management (multi-NIF). Members and their company grants are **shared between Test and Live**: a collaborator is the same person, with the same role and the same ...
A proforma is a non-fiscal commercial document, a formal quote you send a customer before invoicing. It lives on the same `/invoices` resource as any other document, so you work...
**Deprecated.** VeriFactu representation flow for digital signature and AEAT registration, in its account-nested form. Use `CompanyRepresentation` (`/v1/companies/{company_id}/r...
Recurring invoice template management and automated invoice generation. Create templates that automatically generate invoices on a schedule. Supports monthly, quarterly and year...
Read-only access to the API request logs generated by your own API keys (live + test). Inspect method, path, status, timing, and full request/response detail of past calls. Curs...
The tax regimes, percentages, withholdings and exemption reasons BeeL accepts. The same for every credential, and readable before the first NIF exists.
aid: beel-es
name: beel-es
image: https://beel.es/opengraph-image
description: BeeL (beel.es) provides a cloud‑based invoicing platform for Spanish businesses, offering the VeriFactu API that
automates invoice creation, submission to the AEAT, and integration with Stripe. The service includes SDKs, CLI tools, sandbox
testing, and AI‑assisted agents, supporting multi‑NIF, recurring invoices, and compliance features. Documentation, pricing,
and support are publicly available.
url: https://artifacts.apis.io/beel-es/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-30 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-30'
modified: '2026-10-30'
tags:
- invoicing
- Spain
- API
- fintech
- SaaS
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: AgenticAccess
url: agentic-access/beel-es-agentic-access.yml
- type: Plans
url: plans/beel-es-plans-pricing.yml
- type: Spectral
url: rules/beel-es-rules.yml
- type: JSONLD
url: json-ld/beel-es-context.jsonld
- type: Vocabulary
url: vocabulary/beel-es-vocabulary.yml
- type: AgentSkill
url: skills/_index.yml
- type: Webhooks
url: asyncapi/beel-es-webhooks.yml
- type: DataModel
url: data-model/beel-es-data-model.yml
- type: CLI
url: cli/beel-es-cli.yml
- type: Idempotency
url: conventions/beel-es-conventions.yml
- type: Conventions
url: conventions/beel-es-conventions.yml
- type: Security
url: security/beel-es-vulnerability-disclosure.yml
- type: Authentication
url: authentication/beel-es-authentication.yml
- type: Deprecation
url: https://docs.beel.es/guides/deprecation-policy.md
- type: Lifecycle
url: lifecycle/beel-es-lifecycle.yml
- type: ErrorCatalog
url: errors/beel-es-problem-types.yml
- type: Conformance
url: conformance/beel-es-conformance.yml
- type: LLMsTxt
url: llms/beel-es-llms.txt
- type: AgentCard
url: a2a/beel-es-a2a.yml
- type: SecurityTxt
url: well-known/beel-es-security.txt
- type: SecurityTxt
url: well-known/beel-es-mcp-security.txt
- type: SecurityTxt
url: well-known/beel-es-docs-security.txt
- type: SecurityTxt
url: well-known/beel-es-app-security.txt
- type: WellKnown
url: well-known/beel-es-well-known.yml
- type: Hosts
url: hosts/beel-es-hosts.yml
- type: Vendors
url: vendors/beel-es-vendors.yml
- type: Packages
url: packages/beel-es-packages.yml
- type: Sandbox
url: https://beel.es/sandbox
- type: SDKs
url: https://beel.es/api-verifactu/sdks
- type: ChangeLog
url: https://docs.beel.es/changelog
- type: APIReference
url: https://docs.beel.es/invoices/createCompanyInvoice
- type: OAuthScopes
url: scopes/beel-es-scopes.yml
- type: VulnerabilityDisclosure
url: security/beel-es-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/beel-es-domain-security.yml
- type: Website
url: https://beel.es/
- type: Documentation
url: https://docs.beel.es/
- type: Pricing
url: https://beel.es/precios
- type: Blog
url: https://beel.es/blog
- type: Support
url: https://beel.es/contacto
apis:
- aid: beel-es:beel-es-accountcompanies-api
name: beel-es Account Companies API
description: Listing and creating the NIFs of an account, under `/v1/accounts/{account_id}/companies`. Operating on one
NIF is the `Company` resource.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- AccountCompanies
properties:
- type: OpenAPI
url: openapi/beel-es-accountcompanies-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-accountemaildomains-api
name: beel-es Account Email Domains API
description: The domains an account sends its emails from, addressed by `/v1/accounts/{account_id}/email-domains`. The account
in the path is the only source of context, instead of being derived from the credential.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- AccountEmailDomains
properties:
- type: OpenAPI
url: openapi/beel-es-accountemaildomains-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-accountemails-api
name: beel-es Account Emails API
description: The sent-email history of an account, addressed by `/v1/accounts/{account_id}/emails` and `/v1/accounts/{account_id}/email-indicators`.
The account in the path is the only source of context, instead of being derived from the credential. It is the canonical
form of the operations that `Emails` still exposes under `/v1/emails`.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- AccountEmails
properties:
- type: OpenAPI
url: openapi/beel-es-accountemails-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-accountimports-api
name: beel-es Account Imports API
description: 'Onboarding managed accounts in bulk from a file, addressed by `/v1/accounts/imports`. The file is declarative
and the import is re-runnable: each pass applies only what is missing, and previewing is a separate operation with no
effects instead of a boolean flag.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- AccountImports
properties:
- type: OpenAPI
url: openapi/beel-es-accountimports-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-accountrequestlogs-api
name: beel-es Account Request Logs API
description: Canonical form of the request logs, addressed by `/v1/accounts/{account_id}/request-logs`. The account in the
path authorizes the call; the logs returned are always the requests made by you, with any of your API keys in the environment
you authenticate from — never the whole account's traffic, and never another user's. It replaces the operations that `RequestLogs`
still exposes under `/v1/developers/request-logs`.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- AccountRequestLogs
properties:
- type: OpenAPI
url: openapi/beel-es-accountrequestlogs-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-accounts-api
name: beel-es Accounts API
description: 'Account provisioning for partners managing multiple accounts and NIFs. The whole onboarding flow — provisioning,
claim tokens and usage — works with either API key: the account is born inert (no NIF switched on, no keys, no owner),
which is exactly what you are meant to rehearse in Test. Changing a managed account''s access level and ending its management
require a live API key or the dashboard (`403 LIVE_CREDENTIAL_REQUIRED` otherwise): both act on an account that may already
be invoicing, and ending management cannot be undone.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- Accounts
properties:
- type: OpenAPI
url: openapi/beel-es-accounts-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-accountwebhooks-api
name: beel-es Account Webhooks API
description: Outbound webhook subscriptions as a sub-resource of the account itself, addressed by `/v1/accounts/{account_id}/webhooks`.
The account in the path is the only source of context — the credential does not decide it, and the `BeeL-Active-Company`
header plays no part. It is the canonical form of the operations that `Webhooks` still exposes under `/v1/webhooks`.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- AccountWebhooks
properties:
- type: OpenAPI
url: openapi/beel-es-accountwebhooks-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-company-api
name: beel-es Company API
description: 'The company as a resource of its own, addressed by `/v1/companies/{company_id}`. The NIF in the path is the
only source of context: the account that owns it is derived from it.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- Company
properties:
- type: OpenAPI
url: openapi/beel-es-company-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyactivations-api
name: beel-es Company Activations API
description: 'Switching a company on or off in Test or Live, as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/activations`.
The NIF in the path is the only source of context: the account that owns it is derived from it.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyActivations
properties:
- type: OpenAPI
url: openapi/beel-es-companyactivations-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companybranding-api
name: beel-es Company Branding API
description: 'The invoice branding of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/logo`
and `/v1/companies/{company_id}/invoice-customization`. The NIF in the path is the only source of context: the account
that owns it is derived from it.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyBranding
properties:
- type: OpenAPI
url: openapi/beel-es-companybranding-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companycustomerimports-api
name: beel-es Company Customer Imports API
description: Importing customers into a company, addressed by `/v1/companies/{company_id}/customers/imports`. The origin
of the file travels in the body as `source`, so adding an origin never adds a route, and previewing is a separate operation
with no effects instead of a boolean flag.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyCustomerImports
properties:
- type: OpenAPI
url: openapi/beel-es-companycustomerimports-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companycustomers-api
name: beel-es Company Customers API
description: 'The customers of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/customers`.
The NIF in the path is the only source of context: the account that owns it is derived from it. It is the canonical form
of the operations that `Customers` and `Customer Import` still expose under the flat `/v1/customers`.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyCustomers
properties:
- type: OpenAPI
url: openapi/beel-es-companycustomers-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companycustomfields-api
name: beel-es Company Custom Fields API
description: 'The invoice custom fields of a company, addressed by `/v1/companies/{company_id}/custom-fields`: labels a
company adds to its invoices, such as a store, a project or a cost centre, so that people can see, filter and export them.
Each field has a `key` you choose, which never changes, and a list of options: the values already used, per customer or
common to every customer. Test and Live keep separate catalogues. Fields and options are never deleted, only archived,
and an invoice keeps a copy of the label and value it was saved with, so renaming or archiving never changes an invoice
already saved.
Custom fields are informational. They are not part of the VeriFactu record sent to the AEAT and do not enter its hash,
and no mention the invoicing regulations require can be expressed through them. Use `metadata` for technical identifiers
your integration needs and people do not see (order or tenant ids); use custom fields for what a person reads, filters
or exports.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyCustomFields
properties:
- type: OpenAPI
url: openapi/beel-es-companycustomfields-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyemailconfiguration-api
name: beel-es Company Email Configuration API
description: 'The email configuration of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/email-configuration`.
It sets the address the invoice emails of that company are sent from. The `company_id` in the path is the only source
of context: the account that owns it is derived from it.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyEmailConfiguration
properties:
- type: OpenAPI
url: openapi/beel-es-companyemailconfiguration-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyfiscalsummary-api
name: beel-es Company Fiscal Summary API
description: 'The fiscal summary of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/fiscal-summary`.
The NIF in the path is the only source of context: the account that owns it is derived from it.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyFiscalSummary
properties:
- type: OpenAPI
url: openapi/beel-es-companyfiscalsummary-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyinvoicedelivery-api
name: beel-es Company Invoice Delivery API
description: Delivery, bulk operations and exports of a NIF's invoices (send, deliveries, batches, exports, PDF archive),
under `/v1/companies/{company_id}/invoices/...`. Canonical form of `InvoiceDelivery`.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyInvoiceDelivery
properties:
- type: OpenAPI
url: openapi/beel-es-companyinvoicedelivery-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyinvoicelifecycle-api
name: beel-es Company Invoice Lifecycle API
description: State transitions and scheduling of a NIF's invoices (issue, void, corrective, status, schedule), under `/v1/companies/{company_id}/invoices/{invoice_id}/...`.
Canonical form of `InvoiceLifecycle`.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyInvoiceLifecycle
properties:
- type: OpenAPI
url: openapi/beel-es-companyinvoicelifecycle-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyinvoices-api
name: beel-es Company Invoices API
description: 'The invoices of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/invoices`.
The NIF in the path is the only source of context: the account that owns it is derived from it. It is the canonical form
of the operations that `Invoices` still exposes under the flat `/v1/invoices`.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyInvoices
properties:
- type: OpenAPI
url: openapi/beel-es-companyinvoices-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companypaymentconnections-api
name: beel-es Company Payment Connections API
description: 'The payment provider connections of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/payment-connections`.
The NIF in the path is the only source of context: the account that owns it is derived from it. Opening a connection is
the sibling sub-resource `…/payment-connections/authorizations`, because it returns an authorization URL and not the connection
the collection lists.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyPaymentConnections
properties:
- type: OpenAPI
url: openapi/beel-es-companypaymentconnections-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companypaymentevents-api
name: beel-es Company Payment Events API
description: 'The payment events of a company connection, addressed by `/v1/companies/{company_id}/payment-connections/{connection_id}/events`.
The NIF in the path is the only source of context: the account that owns it is derived from it. Events hang from the connection
the `{connection_id}` segment picks, so only the events of that NIF''s connection are reachable.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyPaymentEvents
properties:
- type: OpenAPI
url: openapi/beel-es-companypaymentevents-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyproducts-api
name: beel-es Company Products API
description: 'The product/service catalog of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/products`.
The NIF in the path is the only source of context: the account that owns it is derived from it. It is the canonical form
of the operations that `Products` still exposes under `/v1/products`, and searching is `?q=` on the collection instead
of a path of its own.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyProducts
properties:
- type: OpenAPI
url: openapi/beel-es-companyproducts-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyproforma-api
name: beel-es Company Proforma API
description: Converting a NIF's proforma into a fiscal invoice (`POST /v1/companies/{company_id}/invoices/{invoice_id}/convert-to-invoice`).
The rest of the proforma workflow happens through the regular `CompanyInvoices` operations with `type=PROFORMA` — see
the `Proforma` tag for the full model.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyProforma
properties:
- type: OpenAPI
url: openapi/beel-es-companyproforma-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyrecurringinvoices-api
name: beel-es Company Recurring Invoices API
description: 'The recurring invoice templates of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/recurring-invoices`.
The NIF in the path is the only source of context: the account that owns it is derived from it. It is the canonical form
of the operations that `RecurringInvoices` still exposes under `/v1/recurring-invoices`.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyRecurringInvoices
properties:
- type: OpenAPI
url: openapi/beel-es-companyrecurringinvoices-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyrepresentation-api
name: beel-es Company Representation API
description: 'The AEAT fiscal representation of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/representation`.
The NIF in the path is the only source of context: the account that owns it is derived from it. It is the canonical form
of the operations that `PublicCompanyRepresentations` still exposes under `/v1/accounts/{account_id}/companies/{company_id}/representation/…`,
reshaped as one REST resource — `GET` reads the state, `POST` creates the document, `DELETE` cancels it — instead of five
verbs in the URL.'
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanyRepresentation
properties:
- type: OpenAPI
url: openapi/beel-es-companyrepresentation-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
- aid: beel-es:beel-es-companyseries-api
name: beel-es Company Series API
description: The invoice series of a company as a sub-resource of the company itself, addressed by `/v1/companies/{company_id}/series`.
The NIF in the path is the only source of context. It is the canonical form of what `InvoiceSeries` still exposes under
`/v1/configuration/series`.
humanURL: https://docs.beel.es/
baseURL: https://app.beel.es/api
tags:
- CompanySeries
properties:
- type: OpenAPI
url: openapi/beel-es-companyseries-api-openapi.yml
- type: JSONSchema
url: json-schema/beel-es-create-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-create-corrective-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-recurring-invoice-response-schema.json
- type: JSONSchema
url: json-schema/beel-es-patch-recurring-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-invoice-request-schema.json
- type: JSONSchema
url: json-schema/beel-es-update-recurring-invoice-request-schema.json
# --- truncated at 32 KB (61 KB total) ---
# Full source: https://artifacts.apis.io/beel-es/apis.yml
beel-es API — frequently asked questions
Does beel-es have an API?
Yes. APIs.io lists 54 APIs from beel-es, including beel-es Account Companies API, beel-es Account Email Domains API and beel-es Account Emails API, and 51 more.
Is there an OpenAPI specification for the beel-es API?
Yes. APIs.io indexes 54 OpenAPI specifications for beel-es, each linked for download from this page.
How do I authenticate with the beel-es API?
beel-es documents its authentication (1 scheme). The details are profiled on APIs.io as Beel Es Authentication.
How much does the beel-es API cost?
APIs.io lists 7 pricing plans for beel-es, with each plan's price, limits and inclusions under Pricing Plans on this page.
Is the beel-es API ready for AI agents?
beel-es has a Kin Score of 62.4 out of 100 (strong) and an Agent Readiness score of 82.5 (agent-native), scored by API Evangelist on 2026-10-31.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: