Postback

A way to make sure your users completed the tasks.

Every time a user completes a task, a GET Request will be sent to your postback URL route.

Reasons to Use It

• Prevent bypass with IP checking
• Easily handle your users for reward systems (e.g., giveaways or key systems)
• Unlock more possibilities that can be built on your platform if needed

Enabling Postback

After enabling postback in the panel, your users will need to complete a task with a &puid parameter in the LootLabs link.

For example, if your domain route is:

https://your-domain.com/api/lootlabs

A GET request will be sent there with a few parameters that can help you.

Parameters

• click_id

This parameter helps you identify the user or the specific link they came from. The click_id comes from an attachment parameter in your LootLabs link called puid.

Example LootLabs link:

https://loot-link.com/s?xxxxxx&puid=VALUE

The VALUE in puid will be returned as click_id in the postback request.

Use case: If you have multiple LootLabs links, click_id allows you to determine which link generated the conversion.

• ip

The IP address of the user who completed the task. This is sent automatically, and you do not need to add anything extra to the LootLabs link.

Use case: Useful for detecting fraud or bypass attempts. You can validate that the task was completed by a real user.

• unique_id

A unique ID for each completed task. This ensures that you can differentiate between requests and prevent duplicate processing.

Example Postback URL

When the postback is triggered, LootLabs will send a GET request to your specified URL with the parameters mentioned above. For example:

https://your-domain.com/api/lootlabspostback?click_id{CLICK_ID}ip={IP}&unique_id={UNIQUE_ID}

Setup

You can setup the Postback feature by navigating to the Advanced tab in your LootLabs panel and putting the correct details.

Updated on: 25/08/2025