AcquisityDeveloper Docs
Practical guides

Track background work

Tell the difference between accepted, running and finished.

Some actions take time. An HTTP 202 Accepted response means Acquisity accepted the work and created an operation to track it.

  1. Read the response's Location header, which points to /v1/operations/{operationId}.
  2. Call Get operation with your authorized key.
  3. Check status. Keep polling while it is queued or running, allowing time between requests and respecting rate limits.
  4. At succeeded, failed, or cancelled, inspect the result or error. For needs_attention, inspect the result and follow the action-specific guidance below.
StatusMeaning
queued / runningWork has not finished.
succeededThe operation completed; inspect result for the endpoint-specific outcome.
failedWork failed; inspect its error before deciding whether to retry.
cancelledWork was cancelled. Do not report success.
needs_attentionThe operation needs attention. Do not report success or assume its external effects were cancelled.

For campaign lead imports, needs_attention with result.dispatchStatus: "timed_out" means provider completion was not confirmed within the waiting window. Uploading may still finish. Keep the operation ID and check it again later; a confirmed late completion can update that same operation to succeeded with the final counts. Do not resubmit with a new idempotency key. Other attention results need investigation rather than automatic retries.

Read the outcome carefully: campaign lead search succeeds when dispatched. The leads arrive later. Other actions return their own documented result fields.

Organization-owned operations can only be read by that organization; user-owned operations by that user. Preserve the operation ID if your integration times out so it can check the existing work instead of submitting it again.