Skip to main content
Conductor’s interactive endpoint documentation lets you execute real requests to Conductor’s Data API without having to build a full client first. Use it to validate filters, inspect response schemas, and confirm async query behavior before implementation.

​
How to use the interface

1

Open an endpoint with interactive controls

Navigate to a Data API endpoint page and use the built-in request form:
2

Set authentication inputs

Add apiKey and sig as query parameters, then include X-API-GATEWAY-KEY in headers. Remember: The sig must be re-generated every five minutes.
3

Send an initial POST request

Provide required body fields such as account_id, start_date, and end_date. Async endpoints return 202 with an executionId.
4

Poll until execution completes

Resend a POST request with executionId (and nextPageId when present) until you receive 200 with executionState: "COMPLETED".
5

Validate response shape

Confirm that the schema and results match what your downstream system expects.
This workflow is ideal for developer handoff: Conductor users can validate inputs in the UI, and then engineers can productionize the exact request and response contract. If you are a non-developer, learn more in the API for Non-Developers article.

​
Endpoints

Each of these endpoints are documented here in the playground: