Set a custom field value on a TaskBatch.
Recognized config keys: batch_id (required), field_name (required), value.
URL
- User APIhttps://productivity.mattering.io/api/user/v1/batch-fields/update/
- Service tierhttps://productivity.mattering.io/api/internal/batch-fields/update/
Body keys (JSON)
| Key | Required | Default |
|---|---|---|
config | optional or conditional | none |
space_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,
"results": [
"..."
]
}
Field names come from the code; values are placeholders (... is a string, 0 a number, dates are ISO 8601).
Errors
| Status | Code |
|---|---|
| 400 | missing_batch_or_field |
| 401 | missing_actor |
| 401 | unauthorized |
| 403 | forbidden |
| 404 | batch_not_found |
Example
curl -X POST "https://productivity.mattering.io/api/user/v1/batch-fields/update/" \
-H "Authorization: Bearer $MATTERING_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"config": "...",
"space_id": "..."
}'curl -X POST "https://productivity.mattering.io/api/internal/batch-fields/update/" \
-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 '{
"config": "...",
"space_id": "..."
}'
Source: MatteringPMCore/internal_api.py (internal_api.internal_update_batch_field)