The Postback API allows advertising systems and partners to transmit events related to user traffic: registrations, deposits, re-deposits, and any custom events. This mechanism ensures accurate attribution of user actions, accurate statistics generation, and timely system response to key events.

Using this API, you can transfer data using either a unique clickid or a combination of user_id and spot, making the integration flexible and versatile. Support for custom events allows you to expand analytics to suit your product's specific needs, automate triggers, and update additional player parameters.

This article describes request parameters, response structure, supported events, usage examples, and potential errors so you can quickly and error-free integrate the Postback API into your tracking process.

🌐Request URL

https://thedinator.com/api/v1/api_send_postback/

Method: GET

✅Required parameters

To identify an event, you must pass one of two options :

1. clickid - unique user click ID

Type: string

2. user_id + spot - used if clickid is missing

Type: string

👉One option is enough: clickid or user_id + spot

3. goal - event type (reg, dep, redep, rebill, custom token)

Type: string

🧩Optional parameters

📌Requirements for sum / sumrd

• the value must be a number
• the use {} is not allowed
• If there is a format error → 400 Bad Request

🎯Supported standard targets

🛠️Custom targets

You can transfer any event if it is in your account's target list.

Examples:

goal=level10

goal=tutorial_complete

goal=kyc_submit

Custom events:

• are recorded in statistics📊
• can trigger system notifications to the user🔔
• can update additional fields in the player profile👤

🔍Query examples

Registration

GET /postback/?clickid=ABC123&goal=reg

First deposit

GET /postback/?clickid=ABC123&goal=dep&sum=100

Re-deposit

GET /postback/?clickid=ABC123&goal=redep&sum=50

Custom event

GET /postback/?clickid=ABC123&goal=level10&sum=1

Without clickid (by user_id + spot)

GET /postback/?user_id=7788&spot=87fa11c2-ff00-44a1&goal=reg

⚠️API errors

Example of error:
{"error": "Subscriber not exists with this clickid"}

✅Successful response

Upon successful processing of any event:
{"success": true}

Sending a Contact event 💬

If you use your own CRM system, we offer the ability to send Contact events to Facebook. To do this, send a request via Webhook via the API.

Request URL:
https://api.mvpproject.io/spot/postback/chat/?user_id=telegram id&spot=spot token

Method: GET

🔧 Request parameters:

user_id — Telegram ID of the subscriber (required)

spot — Spot token (required parameter)

📬 Possible responses from the server:

✅ Successful request (HTTP 200):

❌ Errors:

Invalid authorization (HTTP 403):

User_id not specified (HTTP 400):

Subscriber not found (HTTP 404):