Your business logic, our fiscal backend
Any flow that needs to invoice plugs into BeeL. with one REST call. Event-driven, serverless, background jobs, multi-tenant SaaS — the API adapts to your architecture, not the other way around.
7 days free · no card · Unlimited sandbox · Official Node SDK · Pure REST
Fiscal infrastructure, not rigid templates
Every business has unique flows. BeeL. gives you the fiscal foundation so you can focus on what makes your app special.
Complete fiscal abstraction
You don't need to understand VAT, IRPF or Verifactu. BeeL. encapsulates the complexity. You send business data (customer, lines, amount) and get back a legally valid invoice.
Composes with other services
BeeL. is just another piece of your architecture. Combine it with Stripe, SendGrid, your database or your event bus. Each service does what it does best and you orchestrate the flow.
Event-driven and serverless
Call the API from AWS Lambda, Vercel Functions, Cloudflare Workers, RabbitMQ/Kafka consumers or Sidekiq/Celery workers. HTTPS + JSON, no heavy dependencies.
Multi-tenant with per-tenant API keys
If your app is SaaS, each customer has their own BeeL. account and API key. Store the key in your tenants table and invoice on behalf of the active tenant. Isolated legal entities.
Arbitrary business logic
Volume discounts, promotions, dynamic pricing, tiered commissions. Calculate whatever you need in your app and send the result to BeeL. No templates, no fixed rules.
Drafts and programmatic credit notes
Create invoices in DRAFT status for human review. Issue when confirmed. Emit credit notes referencing the original invoice. The whole fiscal chain, handled by the API.
One POST from any language
Same REST call from Node, Python or cURL. Same base URL in sandbox and production — just change the API key prefix.
Examples use beel_sk_test_. Copy, paste and test in your sandbox without risk.
Common integration patterns
Real architectures developers build with BeeL. Pick the one that fits your stack and adapt it.
- 1
Event-driven: invoice from domain events
Your app emits events (OrderCompleted, SubscriptionRenewed). A consumer listens, calls POST /invoices with Idempotency-Key = event_id and guarantees a unique invoice per event.
Node.js - 2
Serverless: on-demand cloud functions
AWS Lambda, Vercel Functions or Cloudflare Workers receive a payload and fetch BeeL. Respond to the frontend with invoice_id in milliseconds and near-zero per-call cost.
- 3
Background jobs: async invoicing queues
Enqueue jobs with Sidekiq, Celery or Bull. The worker calls BeeL. when it has capacity, updates your DB and notifies the user. Ideal if invoicing shouldn't block the frontend.
- 4
Multi-tenant: one API key per tenant
Your tenants table has a beel_api_key column. When invoicing, read the active tenant's key and call BeeL. with it. Each tenant is an independent fiscal entity.
- 5
Signed webhooks to react to the fiscal lifecycle
Subscribe to invoice.emitted, invoice.email.sent, invoice.cancelled and verifactu.status.updated. Constant-time HMAC-SHA256 verification included in the official Node SDK.
Node.js
