Quickstart — no-code integrator
Call the REST facade from n8n, Make or a script with a derived project token.
You are automating on a schedule, with nobody watching: n8n, Make, Zapier, cron. You want a status code and the same answer every time.
1. Get a token
An organisation administrator derives a project token from a service key (no browser step) — the exact call is in Choose your credential. The secret is shown once; store it in your platform's credential vault.
Do not use a scoped API key (rk_…): it opens no capability. Use the derived token (dga_…).
2. Make a first call
curl https://app.digitalyser.io/api/v1/capabilities \
-H "Authorization: Bearer $DIGITALYSER_TOKEN"200 with the catalogue this token may use. 401 means the token is wrong or revoked.
3. Read an audit
curl https://app.digitalyser.io/api/v1/projects/$PROJECT_ID/audits/overview \
-H "Authorization: Bearer $DIGITALYSER_TOKEN"$PROJECT_ID is the project the token was derived for. Every read endpoint is in the
API reference.
4. In n8n
Use an HTTP Request node, not the MCP Client Tool node (it requires SSE, which is not served —
see Integrations). Set the URL above, authentication to Header Auth with
Authorization: Bearer <token>, and store the token as a credential.
5. Handle the two 429s
Branch on reason, never on the status: rate_limited is worth retrying after Retry-After;
quota_exceeded is not. Details in Limits and quotas.
Next
- Conventions — pagination and replaying a write.
- Cookbook — worked recipes.