API Reference Card
All examples use
ASANA_PAT (a Personal Access Token from Asana Developer Console) and MAVERA_API_KEY. PATs have the same permissions as the user who created them.Prerequisites
1
Create an Asana Personal Access Token
Go to app.asana.com/0/developer-console → Personal Access Tokens → Create New Token. Copy it immediately — it won’t be shown again.
2
Identify project GIDs
Every Asana project, task, and user has a GID (global ID). Find project GIDs in the URL:
app.asana.com/0/{project_gid}/... or via GET /projects.3
Mavera API key
Get your key from Mavera dashboard.
4
Environment variables
Jobs
Rate Limits & Production Notes
Production checklist:
- Authentication: PATs inherit user permissions and don’t expire (but can be revoked). For team automations, use a Service Account with OAuth 2.0.
- Pagination: All list endpoints return max 100 items. Follow
next_page.offsetuntil it’s null. - opt_fields: Always specify
opt_fields— Asana returns minimal data by default. Without it, you get onlygidandname. - Webhooks: For the “Brief → Generate” automation, consider Asana webhooks instead of polling. Create a webhook on the project and trigger generation when a task moves to the “Brief Complete” section.
- Idempotency: Check for existing comments before posting duplicate drafts. Search stories for your bot’s marker text.
- Mavera credits: Monitor at Dashboard.