Skip to content
Connect an agent

Connections

List the accounts you can connect an app as

Your own account, and each organisation where you may publish, each with appAllowed and the reason it cannot take the app the request names (members_only, not_allowed).

GET/user/apps/accounts

TL;DR

QuestionAnswer
What does it do?List the accounts you can connect an app as.
What does it take?request in the query string.
What does it return?Status 200 with a body of type AppAccounts.
What can go wrong?401 not signed in; 429 too many requests. Every failure uses the one error envelope.

What it does

Your own account, and each organisation where you may publish, each with appAllowed and the reason it cannot take the app the request names (members_only, not_allowed). The approval checks again.

Query parameters

FieldTypeRequiredDescription
requeststringnoThe signed authorization request, exactly as the API put it in the consent page address.

Responses

StatusMeaningBody
200The accounts.AppAccounts
401Not signed in.ErrorResponse
429Too many requests.ErrorResponse

Response body

A 200 answer has the type AppAccounts.

FieldTypeRequiredDescription
personalobjectyes
personal.allowedbooleanyes
organisationsobject[]yes
organisations[].idstringyes
organisations[].slugstringyes
organisations[].namestringyes
organisations[].role"owner" | "admin" | "member" | "reader"yes
organisations[].appAllowedbooleanyesFalse when the organisation cannot take the app the request names; reason says why. True when no request was sent, or it did not verify: the approval checks again.
organisations[].reason"members_only" | "not_allowed" | nullyesWhy the organisation cannot take the app: members_only (another organisation registered it for its own members), not_allowed (the organisation's "Only approved apps can connect" does not list it). Null when it can.

See also

DocWhy
API referenceEvery endpoint, and the error envelope
SchemasEvery request and response type
Tool referenceThe operations as callable tools