Quickstart — agency
One token per client project, so a workflow wired for one client cannot reach another's data.
You follow several brands. The model is one connection per project: a token carries exactly one project, for machines as for people.
1. One service key, one token per client
An organisation administrator creates a service key once, then derives a token per client project (the call is in Choose your credential). Revoking the service key revokes every derived token in one gesture.
curl -X POST \
https://app.digitalyser.io/api/organizations/$ORG/agent-service-keys/$KEY/tokens \
-H "Authorization: Bearer $ADMIN_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"projectId":"<client project id>"}'The secret is returned once. Store each token under the client's name in your vault.
2. Read each client's audit overview
curl https://app.digitalyser.io/api/v1/projects/$CLIENT_PROJECT_ID/audits/overview \
-H "Authorization: Bearer $CLIENT_TOKEN"Loop over your clients with their own token each time. There is no cross-project token, by design.
3. Mind the ceilings
Quotas are per project and reset on the first of the calendar month, UTC; your plan sets the ceilings (see Ceilings by plan). One client exhausting theirs does not touch another's.
4. People in the loop
For a human who wants to drive one client from an assistant, use the agent quickstart: the consent screen lets them pick that client's project.