Help Center

API Tokens and Integrations

Create personal API tokens to access the Krokanti Tasks REST API. Build automations, integrations, and custom workflows.

2 min read·Krokanti Tasks Help

Krokanti Tasks provides a REST API for building automations and integrations. Access is controlled via personal API tokens.

API access requires a Pro or Team plan. Free plan accounts cannot generate API tokens.

Creating an API Token

  1. Go to Settings → Security (click your avatar in the top-right, then Settings)
  2. Scroll to the API Tokens section
  3. Click New token
  4. Give the token a name (e.g., "Zapier", "Automation Script", "VS Code plugin")
  5. Copy the token immediately — it's only shown once

Token format: kt_ followed by 40 hex characters.

Store your token securely. Krokanti Tasks stores only a hash of your token, so it cannot be recovered. If you lose it, revoke and regenerate.

Using the API

Include your token in the Authorization header of every request:

Authorization: Bearer kt_your_token_here

Example: List your tasks

curl https://tasks.krokanti.com/api/tasks?projectId=PROJECT_ID \
  -H "Authorization: Bearer kt_your_token_here"

Rate Limits

API requests are rate-limited to 100 requests per minute per token. If you exceed this limit, you'll receive a 429 Too Many Requests response with a Retry-After header.

Available Endpoints

The REST API covers the full task management hierarchy:

ResourceMethodsDescription
/api/spacesGET, POSTList and create spaces
/api/projectsGET, POSTList and create projects
/api/tasksGET, POSTList and create tasks
/api/tasks/[id]GET, PATCH, DELETERead, update, delete tasks
/api/tasks/[id]/assigneesPOST, DELETEManage task assignees
/api/tasks/[id]/labelsPOST, DELETEManage task labels

Full API documentation is available at tasks.krokanti.com/developers.

Revoking Tokens

To revoke a token:

  1. Go to Settings → Security → API Tokens
  2. Click Revoke next to the token
  3. The token is immediately invalidated

Revoked tokens cannot be recovered or re-activated. Generate a new token if you need continued access.

Security Best Practices

  • Use one token per integration — makes it easy to revoke one without breaking others
  • Use descriptive names — "Production Zapier" is better than "Token 1"
  • Rotate tokens periodically — especially after team changes
  • Never commit tokens to version control — use environment variables instead

Start organizing your tasks today

Free forever. No credit card required. Works on any device.

Create your free account →

Related articles

Was this article helpful?

Can't find what you're looking for? Contact support