Stripe connection for automatic invoicing
The homepage says you can connect Stripe so that each payment is invoiced and sent to Verifactu automatically, without changing your own system.
BeeL is an API and developer toolkit for issuing Verifactu invoices from Stripe, REST, SDKs, or a CLI. It helps Spanish businesses and developers register invoices with the AEAT and deliver them to customers with a test environment available.
BeeL is a billing platform built around Verifactu invoice issuance for Spain. It lets developers connect Stripe, call a REST API, use official SDKs, or run commands from the terminal to create and issue invoices that are then registered with the AEAT and sent to the customer.
The product is designed around a draft-to-issue workflow. BeeL provides supporting functions for customer records, webhooks, PDF download, NIF validation, recurring invoices, and bulk operations, so it can fit into both application code and operational billing processes.
The homepage says you can connect Stripe so that each payment is invoiced and sent to Verifactu automatically, without changing your own system.
BeeL exposes invoice, customer, series, webhook, and related endpoints over REST, with OpenAPI 3.0 documentation and a predictable JSON workflow.
The site lists SDKs for Node.js/TypeScript, Java, and Python. They are generated from the OpenAPI specification and include typed models, retries, and webhook verification support where documented.
BeeL provides a command-line interface for invoicing, NIF validation, exports, and other tasks. The CLI is described as sandbox-first and suitable for scripts and agent-assisted workflows.
Test keys use a beel_sk_test_ prefix, while live keys use beel_sk_live_. The sandbox shares the same domain and endpoints as production, but does not send anything to the AEAT.
The API includes endpoints for creating, issuing, correcting, scheduling, and exporting invoices, plus PDF retrieval and webhook events for status updates.
Use the REST API or an SDK to create invoice drafts, issue them, and receive status updates through signed webhooks as part of your product flow.
Connect Stripe and let BeeL turn each payment into a Verifactu invoice that is registered with the AEAT and delivered to the customer.
Use the CLI to run invoice operations from the terminal, return JSON for scripting, and keep sandbox mode active unless production is explicitly enabled.
Use the documented bulk import and customer endpoints to bring in customers or invoices, and use series and recurring invoice features to organize ongoing billing.
Check NIFs against the AEAT census before invoicing to reduce errors that would otherwise cause rejected or incorrect billing data.
You can use the REST API directly, install one of the official SDKs, or use the CLI from the terminal. The site also describes a Stripe integration for automatic invoicing from payments.
Yes. The sandbox is activated with a test API key prefixed with beel_sk_test_. The site says the sandbox uses the same domain and endpoints as production, but nothing is sent to the AEAT.
According to the site, issuing an invoice assigns its number, registers it with Verifactu and the AEAT, and can trigger related webhook events such as status updates.
Yes. The API and CLI both document Idempotency-Key support, so if a request is retried the server can return the original response instead of creating another invoice.
The documented API also includes customers, series, recurring invoices, bulk imports, PDF retrieval, NIF validation, and webhook handling.
트래픽 데이터는 참고용으로만 확인하세요.
| 5월 | 5536 |
|---|---|
| 6월 | 4425 |
| 7월 | 4251 |
아직 트래픽 분석 데이터가 없습니다.
아직 트래픽 분석 데이터가 없습니다.