Skip to main content
Version: 2025-12-18

Creates a job to relaunch multiple target groups

POST 
/demand/accounts/{account_id}/projects/{project_id}/batch-jobs/relaunch-fielding-runs-by-target-group-id

This endpoint creates a bulk job to relaunch fielding runs for a list of specified target group IDs. This action will restart the fielding runs for previously completed target groups. A target group can only be relaunched if it is in a 'completed' state and its completes goal and end date have not yet been reached.

To ensure that the same job is not created multiple times, this endpoint uses an Idempotency-Key from the request header. If a job with the same key has already been submitted, the system will not create a new one but will treat the operation as successful and return the same successful response as for a newly created job. If a target group is already live, the system considers the action successful.

Upon successful submission, the system creates a new bulk job to start the actual processing asynchronously. This means the endpoint returns a response quickly without waiting for the entire bulk operation to complete. If the job is created successfully or if it already existed due to the idempotency key, the endpoint returns a 201 Created status code with the job ID in the Location header.

To check the status of the job, you can use the job ID returned in the Location header with the Retrieve a bulk job status endpoint. The processing of the job will continue even if an operation on an individual target group fails. The final job status will list which target groups were updated successfully and which ones failed.

Request​

Responses​

The job was created successfully. Poll the URL in the Location header to track its status.

Response Headers
    traceparent

    The traceparent header carries the trace ID and parent span ID, as defined by the W3C Trace Context specification. It's used to trace a single request as it moves through multiple services.

    tracestate

    The tracestate header complements the traceparent header by carrying vendor-specific trace information. This allows different services to add their own data to a trace.

    location

    Contains the URL where a new resource can be found, often returned with a 201 Created response. It follows the format defined in RFC 7231.

    Example: /demand/accounts/101/projects/01BTGNYV6HRNK8K8VKZASZCFP0/batch-jobs/relaunch/01BTGNYV6HRNK8K8VKZASZCFP1