Create a target group in draft status
POST/demand/accounts/:account_id/projects/:project_id/target-groups
Create a target group in draft status.
The request body may include both profiles and interlocked_profiles arrays in any of these four ways:
- Only
profiles - Only
interlocked_profiles - Both
profilesandinterlocked_profiles - Neither
Constraint: a given profile (or question) ID must appear in only one of these arrays.
If the same ID is listed in both profiles and interlocked_profiles, the draft will fail to save.
To populate interlocked_profiles, first call the generate interlock endpoint then include the response within your draft body.
For zip profiles, currently, you can add only 999 conditions. In future releases, this limit will be increased.
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 500
Successfully created a Target Group in draft status.
Response Headers
The traceparent header primarily carries essential trace context information, including the trace ID and parent span ID as defined by the W3C trace context specification. It's used to pinpoint the position of an incoming request within the trace graph, facilitating the tracking of distributed operations.
The tracestate header complements the traceparent header by providing additional contextual information, thereby allowing for the enrichment of tracing context and offering more fine-grained control.
A request is not valid and can't be processed.
A request is unauthorized.
A requested is forbidden.
A requested resource isn't found.
A request failed due to an internal error.