Evidence Requests
List what to ask the customer receivables team: open potential rows with a request, grouped by cost unit and framework number, as JSON or a CSV attachment.
GET /v1/money-found/evidence-requests turns the open potential rows that carry a request into a list to send to the customer's receivables team. The rows are grouped by cost unit and framework number, largest first. Each group has the customer, the contracts involved, the total, and one item per row to confirm with the ask in plain words, the amount and the period.
With format=csv the list is returned as an attachment named money-found-evidence-requests.csv, one line per row to confirm. Without it the response is JSON. Like the ledger, the call reads the lever ledger and answers 503 while the first build is still running.
/v1/money-found/evidence-requestsQuery parameters
Response fields (JSON)
cURL: JSON
curl "https://api.talonic.com/v1/money-found/evidence-requests" \
-H "Authorization: Bearer $TALONIC_API_KEY"Response: One group
{
"currency": "EUR",
"groups": [
{
"cost_unit": "4711",
"framework_number": "RV-2024-018",
"customer": "Stadtwerke Beispiel",
"contracts": ["RV-2024-018"],
"total": 5320,
"items": [
{ "lever_id": "recurring_charge_not_invoiced", "row_key": "r_81c2e0", "invoice_type": "RE", "period": "2025-Q3", "ask": "Confirm no invoice was issued for the Q3 2025 base charge.", "amount": 5320, "contract": "RV-2024-018" }
]
}
]
}potential tier that carry a request appear here. A potential row is exposure, not entitlement. This route returns the questions to ask and records no answers.