Quick Start

You can use Svit.One API to interact with the Svit.One ecosystem.

Go to the API reference

Authentication

The project-token API uses a project access token. Send it as a bearer token in the Authorization header:

Authorization: Bearer <project-access-token>

Each token is scoped to its project. Task creation and updates use the token creator's current task permissions, and newly created tasks are attributed to that user.

To create and read People in the token's project, use Contacts REST at https://api-external.svit.one/api/v1/external/people. User-delegated applications use the separate OAuth/MCP flow.

Create and update tasks

For new integrations, create a task with POST /api/v2/external/task:

{
    "name": "Follow up with customer",
    "priority": 0,
    "dueDate": "2026-08-20T15:00:00.000Z",
    "assigneeIds": [42]
}

Update only the fields you want to change with PATCH /api/v2/external/task/{taskId}. Use null to clear a nullable field or an empty assigneeIds array to remove all assignees.

Task statuses are todo, in-progress, review, and done. Priorities are fixed numeric levels ordered from 0 (highest) to 4 (lowest). V2 responses can contain all five values; Space-specific names and colors do not change their numeric identities.

POST and explicit PATCH priority assignments currently accept only 0, 1, 2, and 3. POST still defaults to 3. Omitting priority on PATCH preserves the stored value, including 4; explicitly sending 4 is not yet allowed. No priority is silently remapped.

Existing /api/v1/external/task POST/PATCH routes retain their 0–3 response contract. If a PATCH would leave a Task at priority 4, v1 returns 409 Conflict without changing the Task or its assignees. Use v2 for that update. An explicit change to a supported priority is accepted by either version. Neither version currently provides Task GET or list endpoints.

Responses are checked inside the mutation transaction. A response-contract failure rolls back the Task, assignee, and search-index writes. This does not make POST idempotent: sending the same valid POST twice creates two Tasks. Do not blindly retry an ambiguous network failure.

See the API reference for complete request and response schemas.

You can also connect AI assistants and other MCP clients to your Svit.One projects.

Connect to the MCP server and explore its tools