Skip to content
Read an Activation
.md

Read an Activation

Fetch a single activation by its id. The response is a whitelisted, public-safe view - partner credentials and other secrets are stripped.

Request

GET /api/v2/analyses/activations/{id}

curl "https://console.intuizi.com/api/v2/analyses/activations/42" \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "Accept: application/json"

The {id} must be numeric. To list every activation your company owns, see List, Get & Delete. This is the same read you poll after activating an audience.

Response

The activation is returned inside the standard envelope under data, including its lifecycle status and any datastream results.

{
  "status": "success",
  "code": 200,
  "message": "Resource fetched successfully.",
  "data": [
    {
      "id": 42,
      "description": "Q2 Retail Activation",
      "status": { "id": 104, "name": "Completed" },
      "audience": { "id": 88, "name": "Coffee Buyers NYC" },
      "created_by": { "name": "Jane Doe", "email": "jane.doe@acme.example" },
      "project": { "id": 4, "name": "Retail 2025" },
      "partner": { "name": "TheTradeDesk", "description": "Programmatic DSP" },
      "pricing_model": { "name": "CPM Standard", "price": 2.5 },
      "datastreams": [
        { "name": "standard_delivery", "status": "success", "results": { "uri": "s3://..." } }
      ],
      "created_at": "2025-04-02 10:12:03",
      "updated_at": "2025-04-02 11:40:57"
    }
  ]
}

See API Reference - Activations for the field-by-field contract.

Datastreams

When an activation reaches 104 (Completed), each datastream exposes its result location - read those from the datastreams array in data. Which streams appear here is decided when you create the activation - see Deliver to a Partner Endpoint. Note the ids are not sequential: 105 (DataStreaming) happens before 104 - it is the delivery step that was added later and got the next free id. At 105 the results are still being delivered, and 104 Completed is the only success.

Secrets (partner credentials, endpoint config) are never present in the public read response.

Related