Data Provider Status Messages
Lendflow records a status for each external data-service request. Use these statuses to determine whether a service has not started, is still running, completed successfully, found no matching record, or requires corrective action. Some messages come directly from the provider. Others are normalized by Lendflow so common failures are easier to understand.Where provider statuses appear
The Get Commercial Data response returnsdata.statuses alongside data.commercial_data and data.request_data. Statuses are grouped by provider and, when applicable, by service. Use the optional repeated services[] query parameter to limit the response to specific services.
- Display the status message as returned.
- Present a no-results state instead of the raw message.
- Replace a technical provider response with clearer Lendflow wording.
- Continue showing the most recent successful response while identifying that the latest request failed.
internal_error field. That field describes a failed orchestration run and is separate from the provider statuses documented here.
Standard lifecycle statuses
Some providers also return an in-progress message:
Interpret status messages
Do not retry every failure automatically. Correct input and prerequisite errors first, and escalate configuration errors instead of repeatedly running the service.
Provider-specific messages
Text in braces or brackets is dynamic and changes with the application, provider response, request, or service.Experian
Middesk
Ekata
Ocrolus
LexisNexis
Clear
An empty Clear result can be recorded as
Success. Review the Clear data in addition to the status before determining whether a match was found.
Equifax
DNB
MoneyThumb
Codat
Rutter
TaxStatus
What to do when a service fails
- Identify the provider and specific service under
statuses. - Copy the complete status message, including any dynamic provider details.
- Check the corresponding request data for missing or incorrectly formatted information.
- Complete any missing prerequisite, such as uploading PDF bank statements.
- Retry only when the message indicates corrected input or a temporary provider problem.
- If the problem continues, contact Lendflow with the application ID, provider, service, timestamp, and complete message.
FAQ
Why does the Dashboard message differ from the API status?
Why does the Dashboard message differ from the API status?
The Dashboard may replace technical provider text with clearer Lendflow wording or a dedicated no-results state. Use the API’s
statuses value when reporting the complete technical message.Does Success always mean that the provider found a record?
Does Success always mean that the provider found a record?
No. Success means the request completed without a request-level failure. Some services can return an empty result, so review the corresponding provider data as well.
Should I retry every failed status?
Should I retry every failed status?
No. Correct input and prerequisite errors first. Retry temporary availability problems after waiting. Escalate authentication, certification, or configuration errors to your Lendflow account manager or administrator.
Why is an older provider response still visible after a failed run?
Why is an older provider response still visible after a failed run?
The Dashboard can preserve the most recent successful response while identifying that the latest request failed. Review the status and request timestamp before using the displayed data.
What do values in braces or brackets mean?
What do values in braces or brackets mean?
They are placeholders for dynamic information, such as an application ID, business name, provider error, or request name. The returned status contains the actual value.