Overview
REST API documentation for integrating Ukkora with external tools and automations.
Overview
The Ukkora REST API lets you manage tasks and workspaces from external applications, scripts, or automation platforms (Zapier, Make, n8n).
All endpoints are available under the base URL:
https://ukkora.com/api/v1
Quickstart
1. Create a token in your profile settings under API Tokens.
2. Find your workspace ID:
GET /api/v1/workspaces
Authorization: Bearer ukkora_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
{ "data": [{ "id": "550e8400-e29b-41d4-a716-446655440000", "name": "My Team", "role": "owner" }] }
3. Create a task:
POST /api/v1/tasks
Authorization: Bearer ukkora_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Content-Type: application/json
{
"teamId": "550e8400-e29b-41d4-a716-446655440000",
"title": "My first API task",
"deadline": "2026-07-01T09:00:00Z"
}
4. Mark it as done:
POST /api/v1/tasks/{id}/complete
Authorization: Bearer ukkora_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
That's it. The task is now visible in Ukkora with a completion timestamp.
Authentication
All requests must include a personal access token as a Bearer token. You can create tokens in your profile settings under the API Tokens section.
Authorization: Bearer ukkora_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The token is shown only once at creation time — store it in a safe place.
Response format
All responses return JSON in one of two shapes:
{ "data": ... }
{ "error": "...", "message": "..." }
Error codes
| HTTP status | Code | Description |
|---|---|---|
| 401 | unauthorized | Missing Authorization header |
| 401 | invalid_token | Token does not exist or has been revoked |
| 401 | token_expired | Token has expired |
| 403 | forbidden | You do not have access to the requested resource |
| 404 | not_found | Resource not found |
| 422 | validation_error | Invalid request data |
| 500 | internal_error | Internal server error |