Tasker.fit REST API reference and integration guide
Build integrations with the Tasker.fit REST API: authentication, workspaces, boards, tasks, collaboration, QA sessions, file uploads, time tracking, and subscriptions.
Before you begin
Create an active API bearer token and use an account with permission for the requested operation. This guide distinguishes API availability from frontend support.
Planning your workflow
Developer integrations should begin with a read-only request that confirms authentication and scope. Obtain an accessible workspace identifier, then select a board before requesting project data. The frontend API clients and Python SDK model the supported operations and fields, but backend support does not automatically imply that a matching web screen exists. This distinction matters for invitations, time logs, parent-task relationships, and subscription operations.
Handle pagination instead of assuming the first response contains every row. Keep authorization errors separate from an empty successful result, and preserve the API's response envelope when reading data. Before sending a write operation, confirm both the target identifiers and the fields accepted by that endpoint. A client should report a rejected request to its user rather than silently claiming a task, membership, or subscription changed.
Example
An internal reporting script can authenticate with a named bearer token, list accessible workspaces and boards, and page through supported task queries. Time summaries may be read through the developer API even though the task dialog has no complete time-tracking module.
Step-by-step tutorials / 1
Make your first authenticated API request
Create a token in Profile → API Tokens. Store it in your client's private configuration and ensure it is active and not expired.
Send a GET request to /api/company/list/ with the Authorization: Bearer header as shown below.
Read the response's data object and select an accessible company identifier. Use the relevant API client or Python SDK method to request its boards or tasks with supported pagination.
If authentication fails, check token state, expiry, and the header. If access is denied, verify the account's workspace and board permissions.
What to expect: You have confirmed token authentication and can use the supported developer operations listed below.
API guides and endpoint references
Choose the area you are integrating. Each guide includes a workflow, request parameters, JSON payloads, and cURL examples for individual operations.
API authentication, tokens, and account access
Authenticate REST integrations with bearer tokens, understand JWT browser sessions, manage credentials, and read account information.
8 request examples →Workspace, membership, and invitation API
Create and update companies, discover workspace members, send invitations, and accept or decline an invitation through the API.
14 request examples →Board, column, tag, and feature API
Discover project boards, configure Kanban columns, create colored tags, update board features, and manage board membership.
16 request examples →Task CRUD, search, templates, and bug-report API
Create, retrieve, update, archive, clone, and delete tasks, filter task lists, instantiate templates, and submit structured bugs.
13 request examples →Comments, reactions, checklists, and activity API
Build task discussions, attach evidence, manage checklist steps, and retrieve task or board activity logs through REST endpoints.
14 request examples →QA scenarios, test cases, and session API
Automate test-suite setup, start review sessions, record passed or failed cases, create linked bugs, and finish QA runs.
15 request examples →File attachments and task time-log API
Upload multipart files, associate attachments with tasks or comments, download protected files, and manage recorded task time.
8 request examples →Subscription, checkout, and support API
Read tariff plans and usage, create payment checkouts, review transactions, cancel subscriptions, and submit support tickets.
8 request examples →Base URL, requests, and responses
The base URL is https://tasker.fit/api. Keep the trailing slash on endpoint paths. Integrations send Authorization: Bearer with an active API token. Web sessions use Authorization: JWT with an access token; a refresh token belongs only in the session-refresh request.
company_id identifies the workspace and board_id identifies the board. Discover identifiers through API lists: display names and visible task numbers do not replace internal IDs. Examples separate URL query parameters from JSON bodies. Send Content-Type: application/json for JSON; file uploads use multipart/form-data.
Lists support page, limit, and q where shown in the reference. Send array filters as repeated keys, for example assignee_ids=12&assignee_ids=18. Check each endpoint's supported fields instead of copying filters between unrelated lists.
GET /api/task/list/?company_id=demo&board_id=product&page=1&limit=20&assignee_ids=12&assignee_ids=18Successful responses wrap payloads in data. Collection names depend on the endpoint, such as companies or tasks. Check the HTTP status and response content before reading data: validation errors, access failures, and missing objects require separate handling. Some operations, including deletion, may not return a data object; file downloads redirect to storage.
For 401, check the authorization header, token expiry, and token state; for 403, check roles and workspace or board access. For 404, verify identifiers and scope. Correct fields using validation feedback. Avoid automatically repeating creation after an ambiguous network failure: first check whether the object was already created.
Example
curl --request GET 'https://tasker.fit/api/company/list/' \
--header 'Authorization: Bearer <your-api-token>'
# Successful responses wrap payloads in data:
# { "status": "success", "data": { "companies": [...] } }Feature reference
Accept or decline workspace invitations through the API
List an account's workspace invitations and accept or decline an invitation using its invite code. Frontend API hooks exist, but the reviewed application screens do not expose the recipient workflow.
Workspace member role updates through the API
Update an existing workspace member's role through the company-members API. The current workspace member screen displays roles without offering a role editor.
Workspace deletion through the API
Delete a workspace through the company API when authorized. The reviewed workspace settings screen does not expose a workspace-delete control.
Account deletion through the API
The authenticated member endpoint includes an account-delete operation. The current profile screens do not provide a self-service account-deletion interface.
Parent and child task relationships through the API
Create or update a task with a parent-task relationship using the task API. The current task screens do not provide a complete subtask-management workflow, so this should not be advertised as a finished web-app feature.
Task time logs through the API
List, create, edit, and delete time logs associated with a task. Backend time-log operations record details such as start time, duration, and description, but the frontend time-tracking feature card is currently disabled in the feature gallery.
Task time summaries through the API
Retrieve a task's total spent time from the time-summary endpoint. This supports developer integrations; the reviewed task interface does not contain a working time-summary module.
Subscription payment history through the API
List subscription payment transactions using the backend transaction endpoint or SDK. The current subscription screen focuses on plans and usage rather than a transaction-history interface.
Subscription cancellation and disabling through the API
The backend exposes subscription cancellation and disabling operations, with corresponding support in the API client or SDK where present. The current subscription screen does not expose a cancellation or disable-subscription workflow.
Programmatic management of task and board data
API endpoints support task, comment, checklist, attachment, board, column, tag, and workspace operations, including pagination and relevant filters. Developers can build integrations around these operations while respecting the account's permissions and the API's supported request fields.
Tips & troubleshooting
- Scope board requests to both company_id and board_id where required. IDs, allowed request fields, and permissions vary by endpoint; use the API client's models or SDK for the operation you need.
- API-only deletion and subscription changes affect real data. Verify the target account or workspace and operation before sending a write request.
Frequently asked questions
Are API-only capabilities available in the web interface?
Not necessarily. This page explicitly identifies operations with backend/client support but no complete frontend workflow.
Can the Python SDK replace token permissions?
No. SDK requests remain authenticated API requests and are subject to the same account and project permissions.