Endpoints Overview

All endpoints are under the base URL https://admin.trakk.ai/api/v1 and require a Bearer token.

Method	Path	Cached	Paginated	Description
GET	/me	No	No	Verify token and retrieve client identity
GET	/projects	Yes	Yes	List all projects accessible to your token
GET	/projects/{project}	Yes	No	Detailed metadata for a single project
GET	/projects/{project}/reports	Yes	No	All reports for a project, newest first
GET	/projects/{project}/reports/latest	Yes	No	Current-month completed report, or next non-completed if none
GET	/projects/{project}/reports/last-generated	Yes	No	Most recent completed report (always safe to publish)
GET	/projects/{project}/reports/{report_number}/content	Yes	No	Full generated content for a report
GET	/projects/{project}/keywords	Yes	No	Keywords for a project with content status
GET	/countries	No	No	List all countries
GET	/countries/{country}	No	No	Single country
GET	/languages	No	No	List all languages
GET	/languages/{language}	No	No	Single language
GET	/users	No	No	List users visible to your token
GET	/users/{user}	No	No	Single user

---

Common patterns

Path parameters

All {project}, {country}, {language}, and {user} parameters are integer IDs. {report_number} is an integer in the range 1-26 representing the report's position in the project's delivery sequence.

Embedded user objects

Several endpoints embed user objects (in fields like managing_user, approved_by, managed_by). They all share the same compact shape:

{ "id": 7, "name": "Jane Smith", "role": "Account Manager", "agency": { "id": 12, "name": "Digipartner Agency" } }

agency is null when the user has no associated agency.

Agency field shape

The top-level agency field on a project (e.g. "agency": "Digipartner Agency") is a plain string containing only the agency name. This differs from the agency field inside embedded user objects, which is an object { "id": ..., "name": ... }.