API documentation
Read and change your business over a versioned REST API: contacts and deals, projects and tasks, meetings and bookings, invoices, proposals, tickets and more. JSON in, JSON out, one envelope for every answer.
How it works
Authenticate with a Bearer API key, call a resource, and read a consistent
envelope. Every response carries a meta.request_id — quote it
when you contact support and we can find the exact request in the logs.
A key acts for exactly one business. Anything that belongs to another business answers 404, never 403, so other tenants' records cannot be discovered by watching which error comes back.
Base URL
https://api.digitalagency.tools/v1
Authentication
Authorization: Bearer dak1.<id>.<secret>
A first request
GET /v1/me is the cheapest useful call: it tells you which key
you are using, its scope, and the business it acts for.
Create the key in the panel at Settings → Developers. The quickstart walks through it.
Request
curl https://api.digitalagency.tools/v1/me \
-H "Authorization: Bearer $DA_API_KEY"
Response · 200
{
"data": {
"key": { "id": 3, "name": "Reporting script", "scope": "read" },
"business": { "id": 12, "name": "Brightside Studio", "currency": "EUR", … }
},
"meta": { "request_id": "req_6f1c2a9e0b7d4c31" }
}
What you can reach
Generated from the live route table, so it is always what the API actually serves.
| Resource | Endpoints | Lowest scope |
|---|---|---|
| Account | 4 | read |
| Contacts | 8 | read |
| Deals | 8 | read |
| Projects | 28 | read |
| Tasks | 13 | read |
| Planner | 4 | read |
| Meetings & bookings | 16 | read |
| Products | 17 | read |
| Coupons | 6 | read |
| Invoices | 16 | read |
| Proposals | 10 | read |
| Discoveries | 9 | read |
| Tickets | 8 | read |
| Forms | 4 | read |
| Newsletter | 8 | read |
| Staff | 4 | read |
| Notifications | 3 | read |
| Developers | 13 | read |
Next steps
- Quickstart — a key and a first request in five minutes.
- Authentication and scopes — what a key can do.
- Errors — the error envelope and every type.
- Webhooks — signed events when something changes.
- Endpoint reference — every endpoint, parameter and schema.
- OpenAPI 3.1 description — the machine-readable source of truth.