Get parsed invoice result
get_resultReturns the result of a parse job started by parse_invoice: structured fields (supplier, invoice number, dates, net/VAT/gross, currency, line items) plus export links for accounting systems.
Use when: you already have a job_id and want its status or its extracted data. Do not use when: you have no job_id yet — start with parse_invoice. Do not poll in a tight loop: one call every few seconds is enough, text PDFs and XML usually finish in under a minute.
Side effects and cost: none. Does not touch the prepaid balance, so repeated polling is free; a failed job stays failed.
Parameter interactions and edge cases: job_id belongs to the key that created it, so a job started with one key is invisible to another. A pasted URL or a document id from another system returns 404 rather than a guess. A job that failed stays failed — polling it again will not resurrect it; start a new parse_invoice call instead.
Returns: {ok, result}, where result.status is queued, processing, done or failed; on done it also carries fields and export links.
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": {
"job_id": "<job_id>"
},
"name": "get_result"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | Job identifier from the parse_invoice response, for example "2507". Scoped to the API key that created it: another key gets 404. Accepts the numeric id, not a URL. | |
| api_key | No | DueBuddy API key (starts with dd_). Omit it when the server was added with an X-Api-Key header or DUEBUDDY_API_KEY is set. Must be the same key that started the job. |