3 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.
Chirply's client-account API uses the subaccounts domain. Call subaccounts.list from an agency account with the Reseller client-account entitlement to retrieve its child accounts and allowance. The product calls them client accounts; the stable API names remain subaccounts.list, subaccounts.create and subaccounts.update.
It returns the agency's client accounts and allowance in data.result: total, max_subaccounts and subaccounts. Client records include id, name, slug, status and created_at. The request body is an empty object.
What access is required?
Use an agency account with the Reseller client-account entitlement. Listing needs read scope; creating or editing needs write scope and admin-level authorization. Creation is also subject to the plan's client-account allowance.
Does a client ID switch the credential's account?
A returned client ID identifies the child account. It does not change the account a credential acts for. Verify the intended account with GET /api/v1 and authenticate for that account before accessing its CRM records.
Create a client account
subaccounts.createwriteadmin only
Create a client account under this agency. The URL slug is derived from the name and de-duplicated automatically. Fails once the reseller plan's client account allowance is used up.