Status Codes

There are two distinct kinds of “status” in the Intuizi API. Do not confuse them.

1. HTTP / envelope code

The transport-level result of the request. This is the HTTP status code, and it is mirrored in the code field of the envelope.

2. Business lifecycle status

Audiences and activations are processed asynchronously. A read of one of those resources includes a lifecycle status inside data that is separate from the HTTP code. A 200 OK simply means “we successfully told you the current state”; the lifecycle status tells you whether the underlying job has finished.

104 Completed is the only success. A build that stops at 107 Additional Info or at a 4xx error state has failed and does not change again: stop polling, fix the cause, and create it again. Both send the audience.failed or activation.failed webhook. At 107 the worker stopped the build and said why, and Audience Manager shows the reason. A resource at 106 Expired has aged out and does not change again either.

A Lookalike Model you cancel reads 108 Modeling until the run reaches its next checkpoint and stops, then ends at 400 Error, which Audience Manager shows as Cancelled on request. A cancel that arrives once the result is already being published is ignored, and the run completes at 104.

The full create-then-poll flow is described in The Async Model.

3. Cohort status scale (1-5)

Cohorts do not use the 1xx audience/activation lifecycle - they run on their own small scale. Poll GET /api/v2/analyses/cohorts/{id} until it reaches 4 Completed before using the cohort in an audience.

4 and 5 are final, so stop polling at either. A cohort that failed before failures were reported as 5 can still read the error code it failed with, which the API names Unknown. Treat that as a failed import too. What to do after a failed import depends on the source:

• file_uri: fix the file, then create the cohort again.
• upload_reference: the failed create used the reference up, so upload the file again for a new reference.
• audience_id with a regular audience: the failed cohort still counts as the audience’s one cohort, so delete it before creating from that audience again. A Lookalike Model audience needs no delete.

4. POI submission status

POI submissions carry their own small status on the submission read, separate from both scales above. In the order a submission goes through them:

A submission moves from Importing to Waiting on its own. The move from Waiting to Imported or Disabled is a review done by hand, not a processing step, so do not script a wait for it. See My POI Data - Submissions for the read shape.