Update a segment
PUT/cdp/{connection_id}/segment/{id}
Parameters
fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection
idstring required
ID of the Segment
Payload
idstring
Unique identifier for this segment object
created_atdate-time
The date that this segment object was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
The last date that this segment object was updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestring
The name of the segment/audience
slugstring
The data-plane handle/key used to identify segment membership in profiles and destinations
descriptionstring
The description of the segment/audience
definitionstring
The membership rule/query that defines the segment
type enum
Valid values:
"USERS"
"ACCOUNTS"
"LINKED"
The type of entity the segment targets (USERS, ACCOUNTS, LINKED)
compute_mode enum
Valid values:
"REALTIME"
"BATCH"
How the segment membership is computed (REALTIME or BATCH)
sizenumber
The number of profiles currently in the segment
is_activeboolean
Whether the segment is active/enabled
source_idstring
The cdp_source this segment originated from; points to CdpSource
Returns
| Response field | Type | Required | Description |
|---|---|---|---|
id | string | No | Unique identifier for this segment object |
created_at | string (date-time) | No | The date that this segment object was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
updated_at | string (date-time) | No | The last date that this segment object was updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
name | string | No | The name of the segment/audience |
slug | string | No | The data-plane handle/key used to identify segment membership in profiles and destinations |
description | string | No | The description of the segment/audience |
definition | string | No | The membership rule/query that defines the segment |
type | enum | No | The type of entity the segment targets (USERS, ACCOUNTS, LINKED) Values: USERS, ACCOUNTS, LINKED |
compute_mode | enum | No | How the segment membership is computed (REALTIME or BATCH) Values: REALTIME, BATCH |
size | number | No | The number of profiles currently in the segment |
is_active | boolean | No | Whether the segment is active/enabled |
source_id | string | No | The cdp_source this segment originated from; points to CdpSource |
Errors
Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).
{
"statusCode": 429,
"error": "Too Many Requests",
"message": "Too many requests to unified.to API; max requests per minute: N"
}| Status | Error | Meaning |
|---|---|---|
400 | Bad Request | The request was malformed or failed validation. |
401 | Unauthorized | The connection is likely broken; re-authorize it. |
403 | Forbidden | The connection is missing permissions or scopes. |
404 | Not Found | The requested resource does not exist. |
429 | Too Many Requests | Rate limit exceeded (see the two sources below). |
500 | Internal Server Error | An unexpected error occurred. |
501 | Not Implemented | Not supported by this integration. |
Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.
429 Too Many Requests
A 429 has two possible sources:
- The integration's own rate limit, passed through.
- Unified's workspace limit: a rolling 60 seconds, set by plan, with the message
Too many requests to unified.to API; max requests per minute: N.
const options = {
method: 'PUT',
url: 'https://api.unified.to/cdp/5de520f96e439b002043d8dc/segment/5de520f96e439b002043d8d8',
headers: {
authorization: 'bearer .....'
},
data: undefined,
params: {
fields: '',
raw: '',
}
};
const results = await axios.request(options); Are we missing anything? Let us know