Skip to main content
The ImpelLabs API gives your own code the same access that a member has in the app. You can list conversations, add contacts, change agents, start workflows and read credits. Use it for your own scripts and for your own systems.

Base URL

All routes are under one address and one prefix:
Send and read JSON. Set Content-Type: application/json on a request with a body.

A first request

Make an API token in the app, then call a route. This request returns the member that owns the token:
Read Authentication to make a token.

What the token can do

A token acts as the member who made it. It has that member’s role. It sees what that member sees. Agents and channels that are private to someone else stay private. An owner or an admin sees oversight data only: name, owner, status, sharing and spend, never content. The token names its workspace. You do not choose a workspace in a request.

What is in the reference

The API reference group in the sidebar lists every supported route with its fields. Guides for each resource explain how the routes work together. The reference does not list the app’s own routes, such as sign-in and account routes. Those routes need a signed-in session in the app.

Other ways in

  • Your own AI client can use the same access through the MCP server.
  • ImpelLabs can call you. See Webhooks.
  • Partners who run ImpelLabs for their own customers use the Partner API.
Next, read Conventions for errors, paging and time.