Appearance
Xtremepush
Omnichannel engagement platform for iGaming with campaigns, user profiles, and analytics.
| Detail | Value |
|---|---|
| Category | iGaming |
| Base URL | https://api.{region}.xtremepush.com/api/external |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | xtremepush |
Using Xtremepush in a workflow
- Go to Connections and click New Connection.
- Pick Xtremepush from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown. The full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /execute/campaign | Trigger an API-triggered campaign |
POST /info/campaign | Get campaign details |
POST /list/campaign | List campaigns |
POST /import/profile | Import user profiles |
POST /info/profile | Get user profile |
POST /hit/event | Send a real-time event |
POST /batch/event | Batch real-time events |
POST /info/device | Get device details |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /execute/campaign
Trigger an API-triggered campaign
| Detail | Value |
|---|---|
| Operation ID | igaming.executeCampaign |
| Method | POST |
| Path | /execute/campaign |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
apptoken | string |
id | integer |
target | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Xtremepush connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.executeCampaign. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Xtremepush API reference.
POST /info/campaign
Get campaign details
| Detail | Value |
|---|---|
| Operation ID | igaming.campaignInfo |
| Method | POST |
| Path | /info/campaign |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
apptoken | string |
id | integer |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Xtremepush connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.campaignInfo. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Xtremepush API reference.
POST /list/campaign
List campaigns
| Detail | Value |
|---|---|
| Operation ID | igaming.listCampaigns |
| Method | POST |
| Path | /list/campaign |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
apptoken | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Xtremepush connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.listCampaigns. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Xtremepush API reference.
POST /import/profile
Import user profiles
| Detail | Value |
|---|---|
| Operation ID | igaming.importProfiles |
| Method | POST |
| Path | /import/profile |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
apptoken | string |
profiles | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Xtremepush connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.importProfiles. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Xtremepush API reference.
POST /info/profile
Get user profile
| Detail | Value |
|---|---|
| Operation ID | igaming.getUserProfile |
| Method | POST |
| Path | /info/profile |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
apptoken | string |
user_id | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Xtremepush connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.getUserProfile. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Xtremepush API reference.
POST /hit/event
Send a real-time event
| Detail | Value |
|---|---|
| Operation ID | igaming.hitEvent |
| Method | POST |
| Path | /hit/event |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
apptoken | string |
event | string |
user_id | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Xtremepush connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.hitEvent. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Xtremepush API reference.
POST /batch/event
Batch real-time events
| Detail | Value |
|---|---|
| Operation ID | igaming.batchEvents |
| Method | POST |
| Path | /batch/event |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
apptoken | string |
events | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Xtremepush connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.batchEvents. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Xtremepush API reference.
POST /info/device
Get device details
| Detail | Value |
|---|---|
| Operation ID | igaming.deviceInfo |
| Method | POST |
| Path | /info/device |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
apptoken | string |
id | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Xtremepush connection from the Connection dropdown.
- In the Operation dropdown, select
igaming.deviceInfo. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Xtremepush API reference.