Nozbe
PROJECT MANAGEMENT · TASKS
Tasks, projects, comments, and teams in the workspace they belong to.
Connecting Nozbe in practice
Nozbe’s REST API does not live on the app’s hostname — it answers at https://api4.nozbe.com/v1/api — and the Authorization header takes the literal word `apikey` before the token instead of Bearer, which every HTTP client that helpfully adds a scheme gets wrong on the first attempt. Tokens are minted per integration in Settings and can be made global across every space.
Scopes that draw scrutiny
Authorization: apikey <API_token>The only credential, created under Settings → API tokens. A token can be made global so that it reaches all spaces rather than one, and Nozbe documents no read-only variant.
Worth knowing
- Filtering uses bracketed operators on query parameters — [eq], [gt], [lt] — with limit and offset paging, sortBy ordering, and a fields parameter for sparse responses. Using fields matters, because the default response shape is wide.
- The published OpenAPI document at https://api4.nozbe.com/v1/api/openapi.yaml declares version 0.0.1 and describes twenty paths, so anything beyond the documented set is undocumented rather than merely unlisted.
- Nozbe also ships the API description as a PDF at https://files.nozbe.com/nt_api.pdf, which is worth checking when the help-centre page and the OpenAPI file disagree.
- No rate limit is published, so throughput has to be measured against a live token rather than designed for.
Checked against Nozbe API (help centre) (2026-09-29), Nozbe OpenAPI document (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Nozbe behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.