Boost Postbacks

When a player receives an active boost, TapResearch can notify your server via an HTTP postback.

Setup

Boosts need to be enabled for your app title by the TapResearch team, please reach out to your account manager when you are ready to get started.

Once enabled, you can set your boost postback URL in the App title boosts tab under Settings in the Supplier Dashboard. Your URL must begin with https:// and a successful test is required before saving.

Overview

A background job runs every 10 minutes and sends a POST request to your configured URL for each app title that has unnotified active boosts. A boost is included when:

• Its start_date has passed
• Its end_date is at least 1 hour in the future
• It has not yet been notified

If a player has multiple active boosts, only the highest-multiplier boost is sent. On a successful response, those boosts are marked as notified and will not be resent. If the request fails or returns a non-2xx status, the boosts remain unnotified and will be retried on the next run.

HTTP Request

POST <your configured URL>

Property	Value
Content-Type	application/json
Timeout	10s

Payload

The body is a JSON array. Each element represents one app and contains the list of boosted players for that app.

[
  {
    "api_token": "YOUR_API_TOKEN",
    "players": [
      {
        "uid": "player-uid-123",
        "boost": {
          "start_date": "2026-03-17T12:00:00Z",
          "end_date": "2026-03-17T13:00:00Z",
          "boost_tag": "birthday_boost",
          "boost_display_name": "Birthday Bonus",
          "boost_multiplier": 2.0,
          "boost_expiration_date": null
        }
      }
    ]
  }
]

Payload fields

Field	Type	Description
api_token	String	The API token for the app the player belongs to
players	Array	List of boosted player objects for this app

Player object

Field	Type	Description
uid	String	The player's unique identifier
boost	Object	The active boost details

Boost object

Field	Type	Description
start_date	ISO 8601	When the boost became active
end_date	ISO 8601	When the boost expires
boost_tag	String	Internal tag identifying the boost type (e.g., "birthday_boost")
boost_display_name	String	User-facing name for the boost
boost_multiplier	Float	The multiplier applied to the player's rewards (e.g. 2.0 = 2x)
boost_expiration_date	ISO 8601	Expiration date for the boost record. Will be null if not applicable.

Response

Your endpoint should return a 2xx status code to confirm receipt. Any other status — or a failed connection — will cause the boosts to be retried on the next job run.