Iterant is in early access. These docs describe the product as it works today.
Iterant Docs

API reference

Every public REST endpoint, generated from the OpenAPI schema and grouped by the resource it reads.

These pages are generated from the OpenAPI schema, so they track the API as it actually ships. Each one lists the path, parameters, and a live response shape.

Everything here is read-only except the agent task routes. Authentication is the same across the whole surface: an itr_ API key minted in the dashboard, sent as a bearer token. See API keys for how to mint and scope one, and the developer overview for how the REST API, MCP server, and agent tasks fit together.

If you want the conversational surface rather than raw endpoints, the MCP server exposes the same data as tools an agent can call directly.

Last updated on

List accessible brands

The brands this credential can read, with their slug, site and how much work is outstanding on each. Call this first when the brand is not already known: every other route takes a `brandSlug`. An org-scoped key returns every brand in the organization; a brand-pinned key returns exactly its own.