Developer
The Developer section gives you two things: a way to authenticate API traffic to your agents, and a way to see what that traffic did. Both surfaces are workspace-wide and work across every agent type — Agent, Data Agent, and Voice Agent.
| Surface | What it is | When to use |
|---|---|---|
| API Keys | A secret token (sk_...) scoped to one or more agent types and (optionally) specific agents | Calling DronaHQ APIs from your backend, scripts, or third-party tools |
| Request Logs | A 30-day rolling feed of every API request authenticated by your keys | Debugging integrations, auditing usage, investigating errors |
A typical setup looks like this:
- Create an API key with the smallest set of scopes the integration needs.
- Use the key from your application via the
api-keyheader. - When something doesn't behave as expected, open Request Logs and filter by that key to see exactly which calls hit DronaHQ and how they responded.
What you can call with a key
| API | Scope needed | What it does |
|---|---|---|
| Outbound Call Dispatch | Voice Agent | Queue one-off outbound calls and track them as a batch |
| Campaigns | Voice Agent | Create, schedule, and control outbound campaigns, and add contacts to them |
These are server-to-server APIs
The api-key header is not on the CORS allow-list, so browsers cannot call these endpoints directly. Call them from your backend — and never ship a key to a browser or mobile client, since a key is a workspace-wide secret.
What's Next
- API Keys — create, scope, and manage tokens that authenticate your API calls
- Request Logs — inspect, filter, and troubleshoot every authenticated request