Marketing
Projects
Projects, sections and tasks: the same thing the team sees in List, Board, Calendar and Timeline.
Create projects (blank or from a template), add tasks with assignees, dates, tags and dependencies, comment, and link the project to campaigns, pages or events. Every change notifies the team just like in the dashboard.
| GET | /v1/projects | Lists projects with progress, open and overdue tasks. Filters: status, customer_id, search. |
| GET | /v1/projects/templates | Available templates (key, sections and number of tasks). |
| POST | /v1/projects | Creates a project, optionally from a template. |
| GET | /v1/projects/{id} | Project with sections, tasks and linked items with their numbers. |
| PUT | /v1/projects/{id} | Changes name, status, dates, owner or customer. |
| DELETE | /v1/projects/{id} | Deletes the project and its tasks. |
| POST | /v1/projects/{id}/sections | Adds a section (board column). |
| POST | /v1/projects/{id}/links | Links the project or a task to a Meta campaign, page, email, event, form, deal or customer. |
| POST | /v1/projects/{id}/tasks | Creates a task or subtask. |
| GET | /v1/project-tasks | Tasks of one project or all of them, filtered by assignee, status and dates. |
| GET | /v1/project-tasks/{id} | Detail: subtasks, checklist, dependencies, files, comments, links and activity. |
| PUT | /v1/project-tasks/{id} | Updates the task; status=done completes it. |
| DELETE | /v1/project-tasks/{id} | Deletes the task and its subtasks. |
| POST | /v1/project-tasks/{id}/comments | Comments; @Name or @email notifies that person. |
| POST | /v1/project-tasks/{id}/checklist | Adds a checklist item. |
Create a project from a template
With template, tasks arrive with section, priority, checklist and dates calculated from anchor_date (the start, launch or event day, depending on the template). Templates: campaign_launch, webinar_event, agency_client and monthly_content.
curl -X POST https://recaudo.app/api/v1/projects \
-H "Authorization: Bearer sk_live_tu_secret_key" \
-H "Content-Type: application/json" \
-d '{
"name": "Lanzamiento de temporada",
"template": "campaign_launch",
"anchor_date": "2026-12-15",
"customer_id": "uuid-del-cliente"
}'
Task fields
| Field | Type | Description |
|---|---|---|
title |
string | Title (required when creating). |
description |
string | Description in Markdown. |
section_id |
uuid | Project section; defaults to the first one. |
parent_id |
uuid | Parent task, to create a subtask. |
status |
string | todo, in_progress, review or done. |
priority |
string | low, medium, high or urgent. |
start_date |
date | Start date (YYYY-MM-DD). |
due_date |
date | Due date (YYYY-MM-DD). |
recurrence |
string | daily, weekly, biweekly, monthly or yearly: completing it creates the next one. |
assignee_ids |
uuid[] | Assignees; replaces the list. |
follower_ids |
uuid[] | Followers; replaces the list. |
tags |
string[] | Tag names; missing ones are created. |
blocked_by_ids |
uuid[] | Tasks in the same project that must be finished first. Cycles are rejected. |
curl -X POST https://recaudo.app/api/v1/projects/{id}/tasks \
-H "Authorization: Bearer sk_live_tu_secret_key" \
-H "Content-Type: application/json" \
-d '{
"title": "Diseñar piezas para redes",
"assignee_ids": ["uuid-del-usuario"],
"due_date": "2026-12-05",
"priority": "high",
"tags": ["Diseño"]
}'
{
"object": "project_task",
"data": {
"id": "uuid-de-la-tarea",
"project_id": "uuid-del-proyecto",
"section_id": "uuid-de-la-seccion",
"title": "Diseñar piezas para redes",
"status": "todo",
"priority": "high",
"start_date": null,
"due_date": "2026-12-05",
"overdue": false,
"blocked": false,
"assignees": [{"id": "uuid-del-usuario", "name": "María López", "initials": "ML"}],
"tags": [{"id": "uuid-de-etiqueta", "name": "Diseño", "color": "blue"}],
"subtasks": [],
"checklist": [],
"comments": [],
"links": []
}
}
What is due and who has it
GET /v1/project-tasks accepts project_id, assignee_id, status (open = anything not done), due_before, due_after, overdue=1 and include_subtasks=1.
Notifications
Assigning, mentioning, commenting and completing notify people in the dashboard, by email and on their phone, same as in the app. Whoever makes the change is not notified.
Links with numbers
type is meta_campaign, landing_page, email_flow, event, lead_form, deal or customer; id is the item id (for Meta, the campaign id). GET /v1/projects/{id} returns their numbers for the last 30 days.
Repeating tasks
Marking a task with recurrence as done creates the next one with the date moved forward and the checklist unchecked.
From the MCP server
The same actions are available as MCP tools in the projects category: list_projects, get_project, create_project, list_project_tasks, create_project_task, update_project_task, comment_project_task and more.