API Postbacks from Lender

Describes basic and extended postback models

Use case

Cashcat needs additional information from a Lender to tune campaigns in social networks and Google. It is a win-win process because we tune companies, especially for your audience.

The more postbacks we get the more qualitative leads you get. So postback integration is the very first thing to do.

Usually, we can use already developed integration with CPA-networks and catch provided postbacks. But Cashcat offers more flexibility and adjustment to your audience. So simple approved/rejected are not enough. Let's dive into Leads life-cycle and study which postbacks we will use in our new integration.

Understanding of the Statuses

status

Description

passed

Lead passed pre-scoring stage, application data correct and valid. Simple checks are passed.

approved

Lead passed scoring stage succesfully.

rejected

Lead didn't pass pre-scoring/scroing stage

pending

Submitted application or a Lender can't made an automated decision and promise to send passed, approved or rejected in the future

get
Postback

https://cashcat.../postback/universal/
Endpoint works with GET requests only. You can send a postback several times, the API has duplicates protection.
Request
Response
Request
Query Parameters
repeat_loan
optional
string
Indicates about repeat loan. true, false
network
required
string
direct for the direct integration with the Lender or a name of a CPA network (ex. best_cpa_network). API with return an extended response for testing purpose if you place here test value
price_map
optional
string
Indicates that revenue parameter will be skipped and Cashcat backend needs to define a revenue parameter from the Contract between Cashcat and the Lender at the end of the month. Possible values: true
token
required
string
Individual access token provided for the Lender. Each request to the API needs a valid token.
ext_id
optional
string
Lender's internal loan contact ID or lead ID or application ID. Used for quickly find a customer in the Lender's CRM when case investigation.
revenue
required
number
Cashcat's reward. 999.99
action_number
required
string
Conversion identifier of the Cashcat's traffic. This ID was sent in the traffic to the Lender.
status
required
string
Postback's status. It could be: accepted , pending , passed, rejected
Response
200: OK
Provided postback has been accepted by Cashcat. All parameters are correct.
{
"status": "OK",
"message": "Postback created"
}
400: Bad Request
Bad request in status parameter
{
"status": "ERROR",
"message": "Wrong or unregistered status"
}
403: Forbidden
Cashcat can't process postback due to wrong token parameter in the URL.
{
"status": "ERROR",
"message": "Token invalid"
}
404: Not Found
Cashcat can't find object in a database with provided identifier. Pay attention, message could be changed or localized in the future.
{
"status": "ERROR",
"message": "Action number not found"
}

Please, use proper API endpoint that depends on the country:

API endpoint

Country

https://cashcat.ph/postback/universal/

Philippines 🇵🇭

https://cashcat.mx/postback/universal/

Mexico 🇲🇽

https://cashcat.vn/postback/universal/

Vietnam 🇻🇳

https://cashcat.com.ua/postback/universal/

Ukraine 🇺🇦

https://cashcat.co.za/postback/universal/

South Africa 🇿🇦

Retries

It's good practice to implement guaranteed postback mechanism to send postbacks to Cashcat with interval if you got unsuccessful http response code. Please take a look on the Response tab above.