Respond to Line of Credit Offer
An introduction to the Respond to Line of Credit Offer endpoint.
Early AccessCredit API endpoints are currently being finalised as part of ongoing product development. While we do not anticipate significant changes, some interfaces, behaviours, and documentation may be refined before general availability.
The Respond to Line of Credit Offer endpoint records the applicant's response to a line of credit offer. Use this endpoint when an applicant accepts or declines a soft pull offer generated as part of the credit application flow.
When an application passes initial checks, an offer is generated and delivered to the client via Thredd’s Event Delivery System (EDS). The client must then call this endpoint to record whether the applicant accepts or declines the offer.
- If the applicant accepts, a hard credit check is performed. If approved, a line of credit and payment card are created automatically.
- If the applicant declines, the application status is updated to
OFFER_DECLINEDand no further processing takes place.
NoteApplicants have 30 days to respond to an offer. If no response is recorded within that period, the application status is automatically updated to
WITHDRAWN.
Prerequisites
To integrate calls to the Respond to Line of Credit Offer endpoint, you need:
- A valid
offer_id, delivered to the client via webhook when an offer is generated following a successful application submission. - Your own user interface, such as a mobile app or web page, to present the offer to the applicant and capture their response.
- A subscription to Thredd webhooks so that you can receive the offer and subsequent application status updates, and communicate them to the applicant via your user interface.
More informationFor more information about the application process, see: Credit Applications and Origination.
Example Request
Record an applicant's response to a line of credit offer by making a POST request to the Respond to Line of Credit Offer endpoint, passing the offer ID as a path parameter.
POST {{baseUrl}}/api/v1/credit/applications/offers/{offer_id}/response
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
offer_id | string | Required | The unique ID of the offer, received via webhook. |
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
accepted | boolean | Required | Whether the applicant accepts the offer. Set to true to accept or false to decline. |
Example Payload
{
"accepted": true
}{
"accepted": false
}Example Response
A successful request returns a 200 HTTP code, confirming that the applicant's response has been recorded.
NoteIf the request contains invalid data or is incomplete, the system returns a
422HTTP error and details of the validation failure.
{
"detail": [
{
"loc": ["body", "accepted"],
"msg": "Field required",
"type": "missing"
}
]
}What Happens Next
After the applicant's response is recorded, the application status is updated and a webhook event is triggered. The application status will be one of the following, depending on the outcome:
| Status | Description |
|---|---|
OFFER_ACCEPTED | The applicant accepted the offer. A hard credit check is now in progress. |
OFFER_DECLINED | The applicant declined the offer. No further processing takes place. |
APPROVED | The hard credit check passed. A line of credit and payment card have been created. |
DECLINED | The hard credit check failed. The application has been declined. |
WITHDRAWN | The offer expired before a response was recorded. |
More InformationYou can view the full status history of the application using the Get Credit Application Timeline endpoint. For more information about the application process, see Credit Applications and Origination.
Updated 1 day ago
