List what the caller may do in an org
The caller's own permissions in the org: a member's, from their role, or an API key's. Needs no permission, only to be in the org, so a dashboard can offer only what its person may do. Every other route still checks its own.
/v1/orgs/{org}/permissionsThe caller's own permissions in the org: a member's, from their role, or an API key's. Needs no permission, only to be in the org, so a dashboard can offer only what its person may do. Every other route still checks its own.
Authorization
bearer An org API key (sk_live_…, sk_test_…), or an access token from the Synq issuer (the synq brand, on the accounts host) for this API.
In: header
Path Parameters
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/v1/orgs/string/permissions"{ "permissions": [ "string" ]}Read the org's usage GET
Its monthly active users in a month against its plan's allowance (above it each is billed, never refused), and its apps and brands against the plan's limits. A user is active in a month once they get tokens in it: signing in, or an app refreshing their tokens, so someone who stays signed in counts each month an app uses their session. Users deleted since still count: they were billed. Needs `org.billing.view`.
Read an org GET
Needs `org.read`, which every member has.