One key, one workspace
Send your personal key in the Authorization: Bearer header. A key has only the scopes you choose and cannot grant more access than your account. Revoke keys from Connections when you no longer need them.
Bring tasks into Tarca and keep your own tools in step with your work. Use the same workspaces, projects, and permissions you already know.
Beta preview documentation. Production availability is pending release verification.
A title is enough. The new task is private to you and starts in My work → Backlog.
Open Settings → Connections → API. Choose one workspace and allow tasks:write. Copy the key when it is shown and keep it in your tool’s secret storage.
Set SUMONGO_API_KEY to your key in your local environment. Set REQUEST_ID to a new UUID for this task. Keep that UUID and the same request body when retrying.
The API uses the workspace selected for your key. Open My work → Backlog in Tarca to find the result.
curl --request POST \
https://tarca.app/api/v1/tasks \
--header "Authorization: Bearer $SUMONGO_API_KEY" \
--header "Content-Type: application/json" \
--header "Idempotency-Key: $REQUEST_ID" \
--data '{"title":"Review the launch checklist"}'Send your personal key in the Authorization: Bearer header. A key has only the scopes you choose and cannot grant more access than your account. Revoke keys from Connections when you no longer need them.
Read workspaces, projects, and tasks. Create or update tasks with tasks:write. Updates also require the current version in If-Match; use an Idempotency-Key for every create or update.
The versioned OpenAPI document describes supported fields, scopes, pagination, and errors. The reference’s test requests go directly to this Tarca instance. Entered API keys are not saved across reloads.
Browse request examples, response schemas, and authentication requirements.