Menu

Batch fields

1 endpoint in the Mattering Productivity API.

POST batch-fields/update/ User APIService tier

Set a custom field value on a TaskBatch.

Recognized config keys: batch_id (required), field_name (required), value.

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/batch-fields/update/
  • Service tierhttps://productivity.mattering.io/api/internal/batch-fields/update/

Body keys (JSON)

KeyRequiredDefault
configoptional or conditionalnone
space_idoptional or conditionalnone

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

StatusCode
400missing_batch_or_field
401missing_actor
401unauthorized
403forbidden
404batch_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": "..."
}'

Source: MatteringPMCore/internal_api.py (internal_api.internal_update_batch_field)

All Productivity resources
Start Free Explore our Products