POST
tabs/manage/
User APIService tier
Create, update, or delete a project tab.
This read is not paginated. It returns at most 8 rows and does not report a total, so a result of exactly 8 may be truncated.
URL
- User APIhttps://productivity.mattering.io/api/user/v1/tabs/manage/
- Service tierhttps://productivity.mattering.io/api/internal/tabs/manage/
Body keys (JSON)
| Key | Required | Default |
|---|---|---|
action | optional or conditional | none |
is_default | optional or conditional | false |
name | optional or conditional | New Tab |
project_id | optional or conditional | none |
tab_id | optional or conditional | none |
user_id | optional or conditional | none |
Keys the view reads. A key not in this list is ignored by the view. Where a key is required only for some actions (for example the action dispatch), the description above says which.
Responses
200 bare JSON object (no envelope)
{
"success": true,
"tab": {
"id": "...",
"name": "..."
}
}
Field names come from the code; values are placeholders (... is a string, 0 a number, dates are ISO 8601).
Errors
| Status | Code |
|---|---|
| 400 | cannot delete the last tab message |
| 400 | invalid action message |
| 401 | missing_actor |
| 401 | unauthorized |
| 403 | forbidden |
| 404 | project_not_found |
| 404 | tab_not_found |
Example
curl -X POST "https://productivity.mattering.io/api/user/v1/tabs/manage/" \
-H "Authorization: Bearer $MATTERING_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"action": "...",
"is_default": false,
"name": "New Tab",
"project_id": "...",
"tab_id": "...",
"user_id": "..."
}'curl -X POST "https://productivity.mattering.io/api/internal/tabs/manage/" \
-H "X-Internal-Secret: $MATTERING_INTERNAL_API_SECRET" \
-H "X-Internal-Org-Id: $ORG_ID" \
-H "X-Internal-User-Email: you@example.com" \
-H "Content-Type: application/json" \
-d '{
"action": "...",
"is_default": false,
"name": "New Tab",
"project_id": "...",
"tab_id": "...",
"user_id": "..."
}'
Source: MatteringPMCore/internal_api.py (internal_api.internal_manage_tab)