beel_get_payment_event
Retrieve a single payment event for a NIF connection to check its automatic invoicing outcome and, if it failed, get the stable failure code to act on.
Instructions
Retrieves a single payment event of the NIF's connection, including the outcome of its automatic invoicing and, when it failed, the stable failure code you can act on.
Not found: an event that does not belong to this NIF's connection returns
404, the same answer an event that does not exist gets, so an event of another NIF is never disclosed.
BeeL API endpoint: GET /v1/companies/{company_id}/payment-connections/{connection_id}/events/{event_id} (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>",
"connection_id": "<connection_id>",
"event_id": "<event_id>"
},
"name": "beel_get_payment_event"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | Identifier of the payment event, as returned by the list operation. | |
| company_id | Yes | Unique identifier (UUID) of the company the events belong to — 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. | |
| connection_id | Yes | Unique identifier (UUID) of the payment connection the operation acts on, as returned by `GET /v1/companies/{company_id}/payment-connections`. A NIF can hold several connections of the same provider, so the provider slug alone does not name one. A connection of another NIF answers `404`, exactly like one that does not exist. |