Taiga REST API Reference
Complete endpoint catalog for the Taiga REST API, split by domain. Official docs: https://docs.taiga.io/api.html
Load the setup skill first for authentication and the global conventions (auth header, base path, pagination, version locking, the resolver) — those rules apply to every endpoint here and are not repeated in each file.
Global conventions (recap)
- Base:
${TAIGA_API_URL%/}/api/v1/... — header Authorization: Bearer ${TAIGA_AUTH_TOKEN}.
- Edits (
PATCH/PUT) require the object's current version (GET first). PATCH = partial, PUT = full.
- Lists paginate (
x-pagination-* headers; ?page=, or header x-disable-pagination: True) and accept ?project=, ?milestone=, ?status=, ?assigned_to= filters.
- Use
/api/v1/resolver to turn project slugs and item refs into numeric IDs.
Domain index
Open the file matching the resource you need:
| Domain |
File |
Covers |
| Auth & users |
references/auth-users.md |
auth (login/register/refresh), applications & application-tokens, users, user-storage, locales, feedback, contact |
| Projects & access |
references/projects.md |
projects (+ tags, like/watch, modules, stats, duplicate, logo), project-templates, memberships, invitations, roles, permissions |
| Epics |
references/epics.md |
epics, related user stories, epic-statuses, epic custom-attributes (+ values), epic attachments |
| User stories |
references/user-stories.md |
userstories (+ bulk order/backlog/sprint/kanban), userstory-statuses, points, US custom-attributes (+ values), attachments |
| Tasks |
references/tasks.md |
tasks (+ bulk), task-statuses, task custom-attributes (+ values), attachments |
| Issues |
references/issues.md |
issues, issue-statuses, issue-types, priorities, severities, issue custom-attributes (+ values), attachments |
| Milestones & wiki |
references/milestones-wiki.md |
milestones (sprints) + stats, wiki pages, wiki links, wiki attachments |
| History & webhooks |
references/history-webhooks.md |
history & comments, attachments overview, webhooks, webhook-logs, notify-policies |
| Search & import |
references/search-import.md |
search, resolver, stats, export/import, importers (Trello/GitHub/Jira) |
How to use a reference file
Each file lists endpoints as METHOD /api/v1/<path> with purpose and key fields. To run one, wrap it with auth and jq:
curl -s -H "Authorization: Bearer ${TAIGA_AUTH_TOKEN}" \
"${TAIGA_API_URL%/}/api/v1/<path>" | jq .
For writes, add -X POST|PATCH|PUT|DELETE, -H "Content-Type: application/json", and -d '<json>' — and include version on edits.
Examples
1---2name: api-reference-23description: This skill should be used when the user asks for "Taiga API endpoints", "Taiga REST API", "Taiga curl examples", "Taiga API documentation", the exact path/method for any Taiga resource, or needs HTTP details for projects, epics, user stories, tasks, issues, milestones, wiki, webhooks, custom attributes, search, or import/export. Index into the full per-domain endpoint catalog.4---56# Taiga REST API Reference78Complete endpoint catalog for the Taiga REST API, split by domain. Official docs: https://docs.taiga.io/api.html910Load the `setup` skill first for authentication and the global conventions (auth header, base path, pagination, `version` locking, the resolver) — those rules apply to every endpoint here and are not repeated in each file.1112## Global conventions (recap)1314- Base: `${TAIGA_API_URL%/}/api/v1/...` — header `Authorization: Bearer ${TAIGA_AUTH_TOKEN}`.15- Edits (`PATCH`/`PUT`) require the object's current `version` (GET first). `PATCH` = partial, `PUT` = full.16- Lists paginate (`x-pagination-*` headers; `?page=`, or header `x-disable-pagination: True`) and accept `?project=`, `?milestone=`, `?status=`, `?assigned_to=` filters.17- Use `/api/v1/resolver` to turn project slugs and item refs into numeric IDs.1819## Domain index2021Open the file matching the resource you need:2223| Domain | File | Covers |24|--------|------|--------|25| Auth & users | `references/auth-users.md` | auth (login/register/refresh), applications & application-tokens, users, user-storage, locales, feedback, contact |26| Projects & access | `references/projects.md` | projects (+ tags, like/watch, modules, stats, duplicate, logo), project-templates, memberships, invitations, roles, permissions |27| Epics | `references/epics.md` | epics, related user stories, epic-statuses, epic custom-attributes (+ values), epic attachments |28| User stories | `references/user-stories.md` | userstories (+ bulk order/backlog/sprint/kanban), userstory-statuses, points, US custom-attributes (+ values), attachments |29| Tasks | `references/tasks.md` | tasks (+ bulk), task-statuses, task custom-attributes (+ values), attachments |30| Issues | `references/issues.md` | issues, issue-statuses, issue-types, priorities, severities, issue custom-attributes (+ values), attachments |31| Milestones & wiki | `references/milestones-wiki.md` | milestones (sprints) + stats, wiki pages, wiki links, wiki attachments |32| History & webhooks | `references/history-webhooks.md` | history & comments, attachments overview, webhooks, webhook-logs, notify-policies |33| Search & import | `references/search-import.md` | search, resolver, stats, export/import, importers (Trello/GitHub/Jira) |3435## How to use a reference file3637Each file lists endpoints as `METHOD /api/v1/<path>` with purpose and key fields. To run one, wrap it with auth and `jq`:3839```bash40curl -s -H "Authorization: Bearer ${TAIGA_AUTH_TOKEN}" \41 "${TAIGA_API_URL%/}/api/v1/<path>" | jq .42```4344For writes, add `-X POST|PATCH|PUT|DELETE`, `-H "Content-Type: application/json"`, and `-d '<json>'` — and include `version` on edits.4546## Examples4748<example>49User: "What's the endpoint to move a user story to another sprint?"50→ Open `references/user-stories.md`. Single story: `PATCH /api/v1/userstories/{id}` with `{"milestone": <id>, "version": <v>}`. Many at once: `POST /api/v1/userstories/bulk_update_milestone`.51</example>5253<example>54User: "How do I list all issues assigned to me that are still open?"55→ Open `references/issues.md`. `GET /api/v1/issues?project=<id>&assigned_to=<userId>&status=<openStatusId>`. Use `GET /api/v1/issues/filters_data?project=<id>` to discover status IDs.56</example>5758<example>59User: "Give me the curl to create a webhook on project 7."60→ Open `references/history-webhooks.md`. `POST /api/v1/webhooks` with `{"project":7,"name":"CI","url":"https://...","key":"<secret>"}`.61</example>
agents-store