2 operations. Call each with POST https://app.chirply.io/api/v1/actions/<name> and a bearer token; the response is { "data": { "action", "summary", "result" } }. A read badge means the operation changes nothing; write requires the credential’s write scope.
Which account am I in
accounts.currentread
Report the workspace this call is running in: its id, name, whether it is an agency or a client account, and — for an agency — whether this credential can also reach the client accounts underneath it. Call it when you are unsure which workspace you are about to write to. Read-only; changes nothing.
Also answers to whoami, which workspace, current account, what org am I in.
Over MCP the same operation is the tool accounts_current at https://app.chirply.io/api/mcp, same bearer token, same input.
Client accounts you can work in
accounts.listread
List the client accounts this credential can act inside — the separate workspaces an agency runs for each of its clients. Returns each one's id, name, slug and status. To run any other action inside one of them, send the account's id in the 'X-Chirply-Account' header (REST) or as the 'account' argument (MCP); leave it out and you act in your own workspace. Returns an empty list for a workspace that has no client accounts, and for a credential deliberately restricted to its own workspace. Read-only; changes nothing.
Also answers to list sub-accounts, list client workspaces, which accounts can I manage, locations, child accounts.
Parameters
Field
Type
Required
Description
include_inactive
boolean
optional
Include client accounts that are suspended, cancelled or archived. Defaults to false — those accounts exist but refuse machine calls, so acting in one will fail.