beel_delete_customers_bulk
Delete multiple customers by IDs in a single bulk request. Deletes eligible customers, returns per-row status for those that cannot be deleted (e.g., have invoices). Frees identifiers for reuse.
Instructions
Deletes the customers listed in ids from this company (NIF). The operation is partial:
the customers that can be deleted are deleted, and the rest keep their place in
customers_deletion with the status that explains why. That is why it answers 200 with a
body instead of 204, and why it answers 200 even when no row could be deleted.
Each deletion has the same semantics as
DELETE /v1/companies/{company_id}/customers/{customer_id}: the customer is retained
internally for tax record-keeping purposes but is no longer exposed by the API, its
identifier is released for reuse, and invoices already issued to it keep their own copy of
the recipient's details. Deleting is not deactivating: deleting frees the identifier, so the
same NIF can be registered again, while PATCH with active: false leaves the customer
where it is with its NIF still taken. A customer that has invoices cannot be deleted and
comes back with row status HAS_INVOICES.
Endpoint: DELETE /v1/companies/{company_id}/customers/bulk
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | Comma-separated customer IDs | |
| company_id | Yes | NIF (company) the operation acts on. 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 NIF you do not reach answers `403`, and so does a NIF that does not exist, so the existence of a NIF in another account is never disclosed. |