Create Recurring Task

POST 
/projects/recurring-tasks

Creates one recurring task definition. There is no list endpoint and no list binding. The schedule uses rruleOptions (intervalType, not a raw RRULE string). owners and contactIds are the recurring fields — task create uses assignees and contactId. Requires projects/tasks.recurring.write.

Request

Version stringrequired

API Version

Available optionsv3

locationId string

Location id. Required for channel: APP. Ignored for OAuth/PIT — those use the location on the auth token. Do not send in path, body, or headers.

application/json

application/json

Body

Bodyrequired

titlestringrequired

Name of the task

descriptionstring

Description of the task

contactIdsstring[]

Contact Id

ownersstring[]

Assigned To

rruleOptionsobjectrequired

Recurring rules

ignoreTaskCreationboolean

Create initial task or not

Example (auto)

{
  "title": "Task Name",
  "description": "Task Description",
  "contactIds": [
    "sx6wyHhbFdRXh302Lunr"
  ],
  "owners": [
    "sx6wyHhbFdRXh302Lunr"
  ],
  "rruleOptions": {
    "intervalType": "hourly",
    "interval": 1,
    "startDate": "2025-07-23T10:00:00.000Z",
    "dueAfterSeconds": 600
  },
  "ignoreTaskCreation": true
}

application/json

Successful response

application/json

Schema

Schema

recurringTaskobject

Recurring task record

Example (auto)

{
  "recurringTask": {
    "id": "6a102435124ecfb348bd5511",
    "title": "Daily standup prep",
    "locationId": "ve9EPM428h8b87FE9C12Kg",
    "deleted": false,
    "dueAfterSeconds": 3600,
    "rruleOptions": {
      "intervalType": "daily",
      "interval": 1,
      "startDate": "2026-09-20T10:00:00.000Z",
      "dueAfterSeconds": 3600
    }
  }
}