Update delivery destinations

PUT

/v1/settings/delivery-destinations

curl --request PUT \
  --url https://dev-api.infiniteaudience.ai/v1/settings/delivery-destinations \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "destinations": [ { "type": "download" } ] }'

• Development API Server

Replaces the org’s configured delivery destinations (GCS, LiveRamp, Narrative). Requires ‘account’ scope.

Authorizations

• bearerAuth

Request Body^required

Media typeapplication/json

object

destinations

required

Array<object>

One of:

object

Direct file download — exports are placed in GCS and returned as presigned download URLs.

object

type

required

string

Allowed value: download

object

Push to a LiveRamp seat for identity resolution and onboarding. liveramp_seat_id is required for the routing to work.

object

type

required

string

Allowed value: liveramp

liveramp_seat_id

required

LiveRamp seat ID that identifies the target onboarding seat.

string

object

Push to a Narrative.io dataset for data marketplace distribution. narrative_dataset_id is required for the routing to work.

object

type

required

string

Allowed value: narrative

narrative_dataset_id

required

Narrative.io dataset ID that identifies the target dataset.

string

Responses

200

Destinations updated.

Media typeapplication/json

object

ok

required

boolean

Example

{
  "ok": true
}

400

Invalid request — malformed body, missing required attribute, or failed validation. See error and message for details.

Media typeapplication/json

object

error

required

Stable machine-readable error code (e.g. INVALID_STATUS_TRANSITION, BILLING_INSUFFICIENT_BALANCE). Always present.

string

message

Human-readable explanation of the error.

string

code

Alternate machine-readable code — present on some endpoints as an alias for error for backward compatibility.

string

request_id

Opaque support/debug identifier when available.

string

key

additional properties

any

Examples

Examplevalidation_error

{
  "error": "Bad Request",
  "code": "MISSING_SEGMENTS",
  "message": "segment_ids is required for filter audiences."
}

401

Missing or invalid Bearer token. Obtain one via POST /v1/auth/token. When a token was supplied but rejected, code distinguishes TOKEN_EXPIRED (the token’s lifetime has passed — request a new one via POST /v1/auth/token and retry) from TOKEN_INVALID (malformed or revoked — re-authenticate).

Media typeapplication/json

object

error

required

Stable machine-readable error code (e.g. INVALID_STATUS_TRANSITION, BILLING_INSUFFICIENT_BALANCE). Always present.

string

message

Human-readable explanation of the error.

string

code

Alternate machine-readable code — present on some endpoints as an alias for error for backward compatibility.

string

request_id

Opaque support/debug identifier when available.

string

key

additional properties

any

Examples

{
  "error": "Unauthorized: Missing or invalid Authorization header"
}

{
  "error": "Unauthorized",
  "code": "TOKEN_EXPIRED",
  "message": "Your session has expired. Please sign in again."
}

403

Token is valid but lacks the required scope for this endpoint. Check the endpoint description for the required scope (discovery, purchase, or account).

Media typeapplication/json

object

error

required

Stable machine-readable error code (e.g. INVALID_STATUS_TRANSITION, BILLING_INSUFFICIENT_BALANCE). Always present.

string

message

Human-readable explanation of the error.

string

code

Alternate machine-readable code — present on some endpoints as an alias for error for backward compatibility.

string

request_id

Opaque support/debug identifier when available.

string

key

additional properties

any

Examples

Examplemissing_scope

{
  "error": "SCOPE_REQUIRED",
  "message": "This endpoint requires the purchase scope."
}