API Postbacks

Describes postbacks to the Cashcat on approved conversions or rejects

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

Lead life-cycle

status

Description

passed

Lead passed pre-scoring stage

approved

Lead passed scoring stage. Will be payed.

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 approved or rejected in the future

repeated

Used to provide information about repeated contracts/sales. When provided, external_id is required.

get
Postbacks from Lender

https://cashcat.ph/postback/lender_id/?request_id=xxxxxxxxxxx&status=pending
Endpoint works with GET requests only. You can send postback several time, API has duplicates protection. Composit unique key for Cashcat backend is request_id + status
Request
Response
Path Parameters
lender_id
required
string
Personal lender ID. Issued by Cashcat upon a request.
Query Parameters
external_id
optional
string
Optional parameter. Used with status=repeat to provide repeat contract/sale ID
price
optional
number
Optional parameter. Could be passed (default price configured in the Cashcat backend). Can be used to update price in the future on goal-based contract between Lender and Cashcat.
request_id
required
string
1) request_id parameter from Affiliate object, please, check previous article for more information: https://developer.cashcat.ph/docs/api-traffic/api-traffic#affiliate or 2) request_id parameter from incoming marked traffic, stored and translated to a Lender in utm_term
status
required
string
Postback's status. It could be: accepted , pending , passed, rejected , repeated
200: OK
Provided postback has been accepted by Cashcat. All parameters are correct.
{
"status": "OK",
"message": "postback accepted"
}
​
400: Bad Request
Cashcat can't process postback due to wrong parameters in the URL.
{
"status": "ERROR",
"message": "not found any identifiers in the request"
"code": 400
}
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": "not found application with provided identifiers"
"code": 404
}

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

API endpoint

Country

https://cashcat.ph/postback/lender_id/

Philippines πŸ‡΅πŸ‡­

https://cashcat.mx/postback/lender_id/

Mexico πŸ‡²πŸ‡½

https://cashcat.vn/postback/lender_id/

Vietnam πŸ‡»πŸ‡³

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

Ukraine πŸ‡ΊπŸ‡¦

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

South Africa πŸ‡ΏπŸ‡¦

Where can I get my lender_id

Easy! Let's contact with integration team! Support​

We're using API Traffic integration. Where to find a proper postback URL?

Use endpoint URL from affiliate section of submitted application, postback_url parameter https://developer.cashcat.ph/docs/api-traffic/api-traffic#affiliate​

Example

Example of the GET request to one of the Cashcat's websites
GET https://cashcat.com.ua/postback/online_lender_company/?request_id=vc7z8pz149q46hy1&status=accepted

Retries

It's good practice to implement guaranteed postback mechanism to send postbacks to Cashcat with interval if you got unsuccessful http response code.

​