Endpoint ·
GET /ai-employeesRead-only endpoint: it returns information and changes nothing. It is not sent inside the
actions array — you call it directly.name required by the actions
that take an AI employee comes from: the API identifies them by name, not by id,
so this catalog is how you find out which names exist before assembling an action.
Each item carries its type:
operative— can be assigned to the conversation and also run.json— can only be run one-off. Assigning it withassign_ai_employeefails withAI_EMPLOYEE_NOT_FOUND.
search— case-insensitive substring of the name (1 to 100 characters). The asterisk*works as a wildcard and matches any sequence of characters;%and_are matched literally.cursor— opaque cursor returned by the previous page innext_cursor. Omit it to request the first page. Do not reuse a cursor across different endpoints: even though the format is identical, each endpoint interprets it over its own data set.limit— AI employees per page. Default20, maximum100.
next_cursor from the
previous response until has_more is false.
Response
items— array of{ name, type }.next_cursor— cursor for the next page;nullwhenhas_moreisfalse.has_more— whether there are more results after this page.
Example
This is a read: theGET neither assigns nor runs anything, it only returns the
available names so you can use them later in an action.
400— invalid query params (INVALID_REQUEST) or corrupt cursor (INVALID_CURSOR).401— missing, malformed or invalid token (INVALID_API_TOKEN).403— the path slug does not match the token’s business (TOKEN_BUSINESS_MISMATCH).429— rate limit exceeded (RATE_LIMIT_EXCEEDED).500— unexpected server error (UNKNOWN_ERROR).
name returned by this endpoint is the one that goes in the ai_employee
field of the actions that take an AI employee:
Assign and unassign AI employee,
Run AI employee and
AI employee assistance. Remember that
persistent assignment only accepts employees of type operative.