Authentication
Create an API key and authenticate your requests.
Quickstart
Make your first request in a couple of minutes.
Endpoints
Browse every endpoint with live request and response schemas.
Errors & rate limits
Error codes, the response envelope, and rate limits.
Base URL
All requests go to a single global host. Neo routes your request to the right region (US, UK, or EU) under the hood, based on your tenant — there are no per-region URLs.The response envelope
Every response uses the same envelope, so your code can handle success and failure consistently. Success — the payload is indata, with request metadata (and pagination, for lists) in meta:
code, a human-readable message, and a request_id to quote to support:
”Agent” means workflow
In the API, agent is what the dashboard and the rest of these docs call a workflow or agent — the/agents endpoints cover triggered workflows, scheduled agents, and chat agents alike. The public name is agent_id.
The API is additive and versioned. New fields and endpoints can appear at any time, so write your client to ignore unknown fields. Breaking changes ship under a new version path with an overlap window — they never change an existing response shape underneath you.
What’s next
Get your API key
Create a key in the dashboard and start authenticating.
Make your first call
A copy-paste request that lists your agents.
