Callbacks
Addcallback_url to a submit request to receive one POST request after the task reaches a terminal state.
Payload
SocQ sends a task summary. The callback does not include normalized result records; useGET /v1/tasks/{task_id} to read paginated records after status is succeeded.
Fields
| Field | Type | Description |
|---|---|---|
task_id | string | Task identifier from the submit response |
feature_code | string | Internal product feature code |
public_id | string | Public API identifier, such as instagram-posts |
agent | string | Internal agent code |
supplier | string | Internal supplier code |
status | string | succeeded or failed |
result_count | integer | Number of returned result records |
output_summary | object | Summary data such as raw JSONL file links |
error_message | string | Failure reason when status is failed |
created_time | string | Task creation time |
finished_time | string | Task completion time |
Read Results
After receiving a successful callback, fetch normalized records from the task endpoint:results.next_cursor on the same endpoint for additional pages:
Callback delivery is best-effort. Keep polling
GET /v1/tasks/{task_id} as a fallback if your endpoint is temporarily unavailable.
