API de u0life

First-Party REST API overview

The u0life First-Party REST API allows external systems, custom automations, and developer scripts to work seamlessly with records owned by a user API key. All endpoints are versioned under /v1/ and support full CRUD for tasks, clients, and projects.

Use the API alongside website components for server-to-server automations: CRM callbacks, website contact forms, support queues, calendar integrations, and custom bots that need to synchronize work with a central u0life workspace.

• Generate a personal API key in u0life -> Integrations (starts with u0_live_).
• Pass the key in Authorization: Bearer u0_live_your_key or header X-API-Key: u0_live_your_key.
• Granular scopes control permissions: tasks:*, tasks:read, tasks:write, clients:*, projects:*.
• Send and receive JSON with Content-Type: application/json.
• IDs such as client_id, project_id, and category_id must belong to the API key owner.

Base task creation request

curl -X POST https://u0life.com/v1/tasks \
  -H "Authorization: Bearer u0_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"title":"Call client","description":"Created from external API","priority":2}'

List tasks request

curl -X GET "https://u0life.com/v1/tasks?limit=50&offset=0&status=0&active=1" \
  -H "Authorization: Bearer u0_live_your_key"

Base client request

curl -X GET "https://u0life.com/v1/clients?limit=50&offset=0" \
  -H "Authorization: Bearer u0_live_your_key"

Responses and errors

Successful operations return HTTP 200/201 with success: true and a data object containing the record details. When updating task status, a top-level gamification feedback object is also returned. Validation or permission errors return success: false with an error code and message.

{"success":true,"data":{"task":{"id":123,"title":"Call client","status":0,"active":1}}}
{"success":false,"error":{"code":"TITLE_REQUIRED","message":"Task title is required."}}