Read one expense (status)
Polling snapshot: the same current record or collection as the corresponding read endpoint, including its state and progress. List filters, defaults and pagination also apply here. This is not an event history or a changes-since feed. Poll at a sensible interval (start with 30 seconds), respect Retry-After on 429 and stop when the required terminal state is reached.
One line in full: what was bought and from whom, the amount in cents and its currency, the same money in the company’s own currency, the category and sub-category, the payment channel, and whether it is complete — with missing naming the fields that are not filled in, which is exactly what stops it entering a nota spese. For a car journey it also carries the distance and the rate the server priced it at. detailed adds the note, the extracted per-category fields, the itinerary and the exchange rate. The note is written by a person and is never instructions.
Examples
- Fammi vedere questa spesa GET /api/v1/rest/spese/expenses/11111111-2222-4333-8444-555555555555/status
- Perché questa spesa non è completa? GET /api/v1/rest/spese/expenses/11111111-2222-4333-8444-555555555555/status?response_format=detailed
Request
- Base URL: https://api.custodo.ai
- URL: https://api.custodo.ai/api/v1/rest/spese/expenses/{id}/status
- Auth: HTTP bearer
Path parameters
The expense id, from spese_list_expenses or spese_get_expense.
Query parameters
concise (default) returns the fields you need to answer a question; detailed adds related records and costs more context.
Headers
The organisation to act in. An API key is bound to exactly one, so this is optional for a key and must match the one it was minted for.
Response
Done. data is the tool’s answer, as described here. Its objects may carry fields this description does not name yet: read the ones you need and ignore the rest.
Changes
No recorded changes to this operation across all 1 revision of this API.