Generate a report
POST/demand/accounts/{account_id}/reports/{report_type}
This endpoint initiates an asynchronous job to generate a report. A successful request immediately returns a 202 Accepted response containing a report_id, which you can use to track the job's progress with the /status endpoint.
Report Types and Rules
The following table outlines the rules for each report_type:
| Report Type | Supported Levels (filter) | Multi-select Rules |
|---|---|---|
completes | account, business_unit, project, target_group | Multiple IDs can be provided for all levels except account. |
reconciliation-eligible-rids | project, target_group | target_group: Yes. project: No (only one ID allowed). |
reconciliations-status | account, project, target_group | Multiple IDs can be provided for all levels except account. |
respondent-analysis | project, target_group | target_group: Yes. project: No (only one ID allowed). |
sample-bought | account, business_unit, project, target_group | Multiple IDs can be provided for all levels except account. |
term-details | target_group | No (only one ID allowed). |
Request
Responses
- 202
- 400
- 401
- 403
- 404
- 500
Accepted report generation request
Response Headers
The traceparent header carries the trace ID and parent span ID, as defined by the W3C Trace Context specification. It's used to trace a single request as it moves through multiple services.
The tracestate header complements the traceparent header by carrying vendor-specific trace information. This allows different services to add their own data to a trace.
A request is not valid and can't be processed.
A request is unauthorized.
A requested is forbidden.
A requested resource isn't found.
A request failed due to an internal error.