Get lead details
GET/partner/lead/:preLoanRequestId
Returns the identifying and contact details of one of your leads, plus their employer and the documents they attached.
This endpoint carries no risk parameters, no evaluation outcome, and no report fields —
no idPreAprobacion and no urlInforme. Those live on
Get an evaluation by lead id, which
takes the same preLoanRequestId you used here.
That asymmetry is deliberate rather than an oversight: this is the personal-data operation, kept to identity and contact, and anyone calling it already holds the lead id needed to ask for the evaluation.
Requires the evaluation module. The lead is resolved first: a partner without the module
gets 404 for a lead that is not theirs and 403 for one that is.
Not found is deliberately uninformative
A lead that does not exist, a lead that belongs to another partner, and a 36-character id
that is not a UUID all return the same 404 with the same body, so the endpoint cannot be
used to discover which leads exist or who holds them. An id that is not 36 characters long is
rejected with 422 before any lookup.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 422
- 429
- 500
- 503
Lead details retrieved successfully
Bad Request - The token is not your current API token
Unauthorized - Missing or malformed token
Forbidden - Partner is inactive, or does not have the evaluation module
Not Found - The lead does not exist, belongs to another partner, or the 36-character id is not a UUID. All three cases return this same response.
Unprocessable Entity - The id is not 36 characters long. The body carries
"message": "ERR_INVALID_UUID_ID".
Too Many Requests - Rate limit exceeded
Internal Server Error - The lead's documents could not be read.
Service Unavailable - The lead could not be read.