Raycast tasks
Create a Raycast task
Create a task with Raycast’s camelCase fields and optional record, meeting, and section links.
POST
Create a task with Raycast’s camelCase fields and optional record, meeting, and section links.
Use an OAuth access token issued to
This request changes workspace data. A timeout does not prove that the write failed; inspect the result before retrying.
kato-raycast. Developer keys cannot call this endpoint. See Raycast authentication.
Required scopes: tasks:write.
Use task options to discover IDs. Invalid assignees, linked records, meetings, or sections return 400. Optional fields may be omitted; request dates use ISO strings.
Parameters
string
required
Trimmed 1–500 characters.
string
Up to 100,000 characters.
string
Workspace status slug from the Raycast status endpoint.
string
no_priority, low, medium, high, or urgent.
string | null
ISO 8601 datetime, or null. This differs from developer task writes.
string[]
Up to 50 workspace auth-user IDs, each 1–200 characters.
integer
Positive minutes, maximum 525,600.
string[]
Up to 10 accessible record IDs.
string[]
Up to 10 accessible native meeting IDs.
string
Task section ID, 1–200 characters.
Response
201 — Returns the resource underdata. Example IDs and values are illustrative.