Account permissions the caller can put on a personal API key
LogsGET /developer/scopes
Returns, sorted and without duplicates, the account permissions the caller holds across the active memberships of every account linked to them (for example invoice.read or payment.create). These are the only scopes a personal API key may carry, and a secret key created now would carry exactly this list. An account holder whose membership lists no explicit permissions counts as holding account.read, invoice.read, payment.create, reading.create, ticket.create, connection.manage and member.invite. Only a signed-in consumer identity may call it; any other principal type receives 403.
Returns
curl -X GET "$CONSUMER_API/developer/scopes" \
-H "Authorization: Bearer sk_test_..."
# No matching CLI command; use cURL or direct HTTP.
const res = await fetch("$CONSUMER_API/developer/scopes", {
method: "GET",
headers: {
Authorization: "Bearer sk_test_..."
}
});
const data = await res.json();
import requests
res = requests.get(
"$CONSUMER_API/developer/scopes",
headers={
"Authorization": "Bearer sk_test_..."
}
)
data = res.json()
req, _ := http.NewRequest("GET", "$CONSUMER_API/developer/scopes", nil)
req.Header.Set("Authorization", "Bearer sk_test_...")
resp, err := http.DefaultClient.Do(req)
{
"data": [
"data"
]
}