Docs Developers
REST API
Keys, requests and limits: everything in the app, over HTTP.
Everything you can do in the app, you can do over HTTP: Missions, tasks, time, Talk, files, agents, invoices and more. The full list of endpoints is in the API reference, which you can try right in the browser.
GET https://nextis.pro/api/v1/tasks/mine
Authorization: Bearer nx_8fK2…
{"data": [{"type": "task", "id": "…", "attributes": {"title": "Pricing page copy", "status": "review"}}]}
- 1Everything is under /api/v1, in JSON:API.
- 2Your key: the request acts as you, in the key's Space, with your role.
- 3What comes back: the records you may see, and nothing else.
Getting a key
-
Open API and MCP
In the app, open your menu at the bottom of the sidebar and choose API and MCP.
-
Make a key
Name it after where it'll be used. Make it read-only if it only needs to look, and give it an end date if it's for a while.
-
Copy it now
The key starts with
nx_and is shown once. Keep it like a password.
Making requests
Send the key as a Bearer token (or in an X-API-Key header). Requests and
answers are JSON:API.
curl https://nextis.pro/api/v1/tasks/mine \
-H "Authorization: Bearer $NEXTIS_KEY"
curl https://nextis.pro/api/v1/tasks \
-H "Authorization: Bearer $NEXTIS_KEY" \
-H "Content-Type: application/vnd.api+json" \
-d '{"data": {"type": "task", "attributes": {"title": "Draft the launch post", "mission_id": "…"}}}'
Limits
-
300 requests a minute per key; past that, the answer is
429until the minute is over. - Read-only keys get
403on anything that changes data. - An expired key, or one of someone no longer in the Space, gets
401.
Seeing what keys did
API and MCP shows each key's last use and the recent changes made through it. Delete a key there to stop it at once.