Tracking a Lead
Read a lead's state and know what each state means for you.
Every lead has a state that moves as FincheckEngine processes it. Read it with the lead id returned when you created the lead.
See GET /api/v2/lead/{hashid} in the API Reference →
Read the lead
cURL
curl "https://your-api-origin/api/v2/lead/k3mN9pQx" \
-H "Authorization: Bearer fce_your_key" \
-H "Accept: application/json"
JSON
{
"state": "dispatched",
"added": "2026-09-29T08:15:42Z",
"first_name": "Thabo",
"last_name": "Molefe",
"intent": "Personal Loans"
}
The response also returns the applicant data stored for the lead. You can only read your own leads: ones created for your account, or submitted with your API key. An unknown id, or another affiliate's lead, returns HTTP 404.
Lead states
Processing
Direct outcomes
Comparisons outcomes
A lead can also be marked rejected or uninterested when a partner or the applicant closes it. Both are final.
How often to check
- Check a Direct lead a few minutes after creating it, then at longer intervals. Most leads leave
receivedquickly. - Stop checking once the lead reaches a final state.
- Keep polling bounded. A
404means theidis wrong or belongs to the other environment, so fix theidrather than retrying. - Single leads have no completion webhook. For many leads at once, use Batch Import, which supports one.