For queries that process large amounts of data, the Data API uses an asynchronous execution model. Instead of holding your connection open (and risking a timeout), you submit a query, receive a tracking ID, and poll for the results at your own pace.Documentation Index
Fetch the complete documentation index at: https://conductor.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Currently, all endpoints in the Data API require async queries.
The async lifecycle
- Initial Request: Submit your query parameters. The API returns a
202 Acceptedstatus along with anexecutionId. - Polling: Send the
executionIdback to the endpoint. If it’s still processing, you’ll get another202 Accepted. Once finished, you’ll get a200 OKwith your data. - Pagination: If your results are large, the completed response includes a
nextPageId. Pass this token in your next request to pull the following page of results.
Response fields
| Field | Description |
|---|---|
executionId | The unique identifier for tracking your specific query. |
executionState | The current status: either "IN_PROGRESS" or "COMPLETED". |
nextPageId | A token for retrieving the next page of results (when available). |
Walkthrough
Submit the initial query
Include all required query parameters specific to the endpoint.Save the
executionId from this response for the next step.Poll for results
Use the
executionId you received. Drop the main query parameters and only send the ID.- Still running? Expect a
202response withexecutionState: "IN_PROGRESS". - Finished? Expect a
200response withexecutionState: "COMPLETED"and your data payload.
Need help? Reach out to the Data Platform Team: [email protected]
