beel_create_invoice_delivery
Sends multiple invoice PDFs as attachments in a single email to specified recipients and reports any invoices that could not be attached.
Instructions
Sends one email carrying the PDFs of several invoices of this company as attachments.
recipients: required, and must carry at least one address; no address is inferred from any profile.Limit: up to 200 invoices per message (
invoice_ids).Failures: invoices whose PDF cannot be attached are reported in
failures, and the message is still sent with the rest.
BeeL API endpoint: POST /v1/companies/{company_id}/invoices/deliveries (reference: https://docs.beel.es)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"company_id": "<company_id>",
"body": "<body>"
},
"name": "beel_create_invoice_delivery"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| company_id | Yes | Unique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed. | |
| idempotency_key | No | Optional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created. |