What can you do with the API?
The Interact REST API lets you integrate Interact into your own systems and workflows. Common use cases:- Trigger an agent job after a data pipeline finishes loading new data
- Fetch job results to display them in an internal dashboard
- List chat sessions for a specific agent or job for audit purposes
Authentication
Every API request requires two headers:| Header | Value |
|---|---|
X-API-Key | Your API key, created in Settings → API |
X-Organization-Id | Your organisation ID, visible in Settings → Organisation |
Getting your API key
Create a new key
Click Create API key, give it a descriptive name (e.g. “Data pipeline trigger”), and select the permissions:
| Permission | What it allows |
|---|---|
agent_jobs_trigger | Trigger agent job runs via the API |
Your first API call: trigger a job
The most common API use case is triggering an agent job. Here’s how:{job_id} with the ID of the job you want to trigger. You can find the job ID in the job’s settings page URL in Interact.
Successful response:
chat_id in the response is the ID of the new chat session created by this run. You can use it to retrieve results later.
Fetch a chat and its results
Once a job run completes, retrieve the full chat including any documents (tables, charts) it produced:- Full message history
- Documents produced by the agent (query results, charts)
- Run metadata (status, timestamps)
List all chats for an agent
Full API reference
Explore all available endpoints, request parameters, and response schemas in the auto-generated API reference below.Turntwo Interact API
Full endpoint documentation generated from the OpenAPI specification.