List recovery cases (the Recoveries work surface)
const url = 'https://api.invogi.com/v1/recoveries?view=open&limit=50&offset=0';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.invogi.com/v1/recoveries?view=open&limit=50&offset=0' \ --header 'Authorization: Bearer <token>'Overdue next actions first, then the most value still open. Saved views follow docs/35_AP_RECOVERY_WORKFLOW_DESIGN.md §10.3. Readable by every role and by API keys.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”A page of cases
object
object
CONFIRMED, IN_RECOVERY and AGREED are set by people (the stage); CREDIT_RECEIVED, PARTIALLY_REALIZED and REALIZED are derived from instruments and applications; the CLOSED statuses from closure.
Active applications only — cash received plus credit applied
Confirmed less verified less closed
Carried over from a RECOVERED invoice outcome
The supplier has recent bills with no recorded payment that could carry an offset
Ledger credits or imported refunds suggested for this case and waiting for a person (see suggestedMatches on the case)
Example
{ "items": [ { "status": "CONFIRMED", "stage": "CONFIRMED", "vatAdjustmentStatus": "REQUIRED" } ]}Invalid request
object
object
Example
{ "error": { "code": "NOT_FOUND" }}Missing or invalid API key
object
object
Example
{ "error": { "code": "NOT_FOUND" }}