Appearance
Optimove
CRM marketing platform for iGaming with customer segmentation, campaigns, and lifecycle management.
| Detail | Value |
|---|---|
| Category | iGaming |
| Base URL | https://api4.optimove.net |
| Authentication | API Key |
| Endpoints | 9 |
| Connector key | optimove |
Using Optimove in a workflow
- Go to Connections and click New Connection.
- Pick Optimove 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 |
|---|---|
GET /General/GetLastDataUpdate | Last data update timestamp |
GET /Model/GetCustomerAttributeList | Customer attributes |
GET /Model/GetLifecycleStageList | Lifecycle stages |
GET /Model/GetMicrosegmentList | Microsegments |
GET /Actions/GetAllActions | Marketing actions |
GET /Actions/GetExecutedCampaignDetails | Campaign details |
GET /Actions/GetPromoCodes | Promo codes |
GET /Customers/GetCustomerAttributes | Customer attribute values |
GET /Segments/GetCustomersByValueSegment | Customers by value segment |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /General/GetLastDataUpdate
Last data update timestamp
| Detail | Value |
|---|---|
| Operation ID | crm.getLastDataUpdate |
| Method | GET |
| Path | /General/GetLastDataUpdate |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getLastDataUpdate. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
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 Optimove API reference.
GET /Model/GetCustomerAttributeList
Customer attributes
| Detail | Value |
|---|---|
| Operation ID | crm.getCustomerAttributes |
| Method | GET |
| Path | /Model/GetCustomerAttributeList |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getCustomerAttributes. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
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 Optimove API reference.
GET /Model/GetLifecycleStageList
Lifecycle stages
| Detail | Value |
|---|---|
| Operation ID | crm.getLifecycleStages |
| Method | GET |
| Path | /Model/GetLifecycleStageList |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getLifecycleStages. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
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 Optimove API reference.
GET /Model/GetMicrosegmentList
Microsegments
| Detail | Value |
|---|---|
| Operation ID | crm.getMicrosegments |
| Method | GET |
| Path | /Model/GetMicrosegmentList |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getMicrosegments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
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 Optimove API reference.
GET /Actions/GetAllActions
Marketing actions
| Detail | Value |
|---|---|
| Operation ID | crm.getAllActions |
| Method | GET |
| Path | /Actions/GetAllActions |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getAllActions. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
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 Optimove API reference.
GET /Actions/GetExecutedCampaignDetails
Campaign details
| Detail | Value |
|---|---|
| Operation ID | crm.getCampaignDetails |
| Method | GET |
| Path | /Actions/GetExecutedCampaignDetails |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
Date | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getCampaignDetails. - 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 Optimove API reference.
GET /Actions/GetPromoCodes
Promo codes
| Detail | Value |
|---|---|
| Operation ID | crm.getPromoCodes |
| Method | GET |
| Path | /Actions/GetPromoCodes |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
Date | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getPromoCodes. - 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 Optimove API reference.
GET /Customers/GetCustomerAttributes
Customer attribute values
| Detail | Value |
|---|---|
| Operation ID | crm.getCustomerAttributeValues |
| Method | GET |
| Path | /Customers/GetCustomerAttributes |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
CustomerIDs | query | string | Yes |
CustomerAttributes | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getCustomerAttributeValues. - 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 Optimove API reference.
GET /Segments/GetCustomersByValueSegment
Customers by value segment
| Detail | Value |
|---|---|
| Operation ID | crm.getCustomersByValueSegment |
| Method | GET |
| Path | /Segments/GetCustomersByValueSegment |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
valueSegmentID | query | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Optimove connection from the Connection dropdown.
- In the Operation dropdown, select
crm.getCustomersByValueSegment. - 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 Optimove API reference.