Skip to main content
You have a dgql_ key and want to know whether it works. This takes about five minutes: one request proves the key, and the table at the end names every way it can go wrong and the fix.

Before you start

  • An API key that starts with dgql_. A Darpan administrator creates it for one tenant and shows it once. If you lost it, ask for a new one; nobody can show it again. See Authentication.
  • Your API host. On hosted Darpan it is https://api.drpn.ai. A self-hosted instance has its own backend URL. The app’s address (app.drpn.ai) is not the API host.

Run your first request

1

Keep the key in an environment variable

The key reads a tenant’s audit findings and run results. Keep it out of your shell history and source code:
Paste the key at the silent prompt and press Enter.
2

Send a query

This query asks for the tenant’s latest reconciliation run. It works on every tenant, including one with no runs yet.
Prefer a browser? The API explorer sends the same request from this site: paste your key, pick Check your key, and press Send.
3

Read the answer

A key that works returns data, and extensions.cost says what the query cost:
"edges": [] is a working key too: the tenant has no runs yet.

When it does not work

Darpan answers a refused key or query with HTTP 200 and an errors list, so read errors, not only the status code. Every other code is listed in Errors.

Next steps

Find the query for your task

Recipes for the questions integrations ask most: this morning’s audit, open findings, one finding, recent runs.

Try every query in the explorer

One example per query, ready to send with your key.