Repair a TASKS-type widget that is missing its backing list, and optionally migrate project-level orphan tasks into the widget's list.
Background: widgets created via the API with a non-canonical widget_type (e.g. lowercase "task_list" instead of "TASKS") historically skipped the backing-list creation step, leaving the widget bound to no list. Tasks subsequently created via manage_task / create_tasks_bulk against such a widget land at project-level (task.list_id = NULL, task.project = widget.tab.project) and are invisible in the widget UI even though they exist. This endpoint provides a one-shot repair: ensure the widget has a backing list, then re-bind the orphan tasks into it.
Payload:
widget_id (required): public_id of the widget to repair.
migrate_task_ids (optional): list of task public_ids to attach to the backing list.
Each listed task gets task.list = backing_list and task.project = None (matching
the post-create state for tasks created against a properly-configured TASKS widget).
Tasks not found in the widget's space are reported in errors; tasks already bound
to the same list are no-ops and not counted in migrated_count.
migrate_project_orphans (optional, default False): when True, sweep every project-level
orphan task (task.project set, task.list NULL) for this widget's project into the
backing list without enumerating ids. Intended for the multi-task-widget case the
read-time self-heal deliberately skips (it can't tell which widget the orphans belong
to); the caller asserts they belong to THIS widget. Unioned with migrate_task_ids.
normalize_widget_type (default True): if True and the widget's stored widget_type has
any lowercase characters, normalize it to uppercase so future create-task calls and
the create-time gate behave consistently.
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/widgets/attach-backing-list/
Service tierhttps://productivity.mattering.io/api/internal/widgets/attach-backing-list/
Body keys (JSON)
Key
Required
Default
migrate_project_orphans
optional or conditional
none
migrate_task_ids
optional or conditional
none
normalize_widget_type
optional or conditional
true
user_id
optional or conditional
none
widget_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.
Configure view settings on up to 50 TASKS widgets in one call.
Mirrors internal_configure_widget_view per-update, but executes the whole batch in a single round-trip and aggregates per-update errors instead of aborting on the first failure. Use this when applying the same status-preset / custom-field-preset / view config across many widgets (e.g. attaching the standard env-var presets to every Dev/Prod widget after bootstrapping a project).
Each update independently writes any provided fields to the widget's config dict. Per-update errors do not abort the batch. The response aggregates a per-widget applied_fields list (only the keys that actually mutated config), plus an errors array describing any widget_not_found / status_preset_not_found / custom_field_preset_not_found / authorization failures.
Authorization is enforced once per project: updates spanning multiple projects are supported, and projects the acting user cannot edit produce per-update errors rather than 4xx-ing the entire batch.
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/widgets/configure-view-bulk/
Service tierhttps://productivity.mattering.io/api/internal/widgets/configure-view-bulk/
Body keys (JSON)
Key
Required
Default
project_id
optional or conditional
none
updates
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.
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/widgets/configure-view/
Service tierhttps://productivity.mattering.io/api/internal/widgets/configure-view/
Body keys (JSON)
Key
Required
Default
custom_field_ids
optional or conditional
none
custom_field_preset_id
optional or conditional
none
filters
optional or conditional
none
group_by
optional or conditional
none
project_id
optional or conditional
none
save_filters_for_all
optional or conditional
none
sort_column
optional or conditional
none
sort_direction
optional or conditional
none
status_preset_id
optional or conditional
none
statuses
optional or conditional
none
user_id
optional or conditional
none
view_mode
optional or conditional
none
widget_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
200bare JSON object (no envelope)
{
"success": true,
"config": "..."
}
Field names come from the code; values are placeholders (... is a string, 0 a number, dates are ISO 8601).
Create / update / delete up to 50 widgets in one call.
Mirrors internal_manage_widget per-operation, but executes the whole batch in a single round-trip and aggregates per-op errors instead of aborting on the first failure. Use this when bootstrapping multiple widgets (e.g. Dev + Prod for several modules) or restructuring tabs in bulk: it avoids the overhead of N HTTP calls and N permission checks.
Per-operation errors do not abort the batch; they are collected in errors while successful operations are committed. Backing-list creation for TASKS-type widgets uses the same canonical naming rules as manage_widget (uppercase widget_type + unique list name suffixed with the new widget's public_id).
Authorization is enforced once per project: operations spanning multiple projects are supported, and projects that the acting user cannot edit produce per-op errors rather than 4xx-ing the entire batch.
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/widgets/manage-bulk/
Service tierhttps://productivity.mattering.io/api/internal/widgets/manage-bulk/
Body keys (JSON)
Key
Required
Default
operations
optional or conditional
none
project_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.
Create, update, or delete a widget on 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/widgets/manage/
Service tierhttps://productivity.mattering.io/api/internal/widgets/manage/
Body keys (JSON)
Key
Required
Default
action
optional or conditional
none
height
optional or conditional
4
position_x
optional or conditional
0
position_y
optional or conditional
0
project_id
optional or conditional
none
tab_id
optional or conditional
none
title
optional or conditional
none
user_id
optional or conditional
none
widget_id
optional or conditional
none
widget_type
optional or conditional
none
width
optional or conditional
12
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.
We use strictly necessary cookies to run this site. With your permission we also use analytics cookies
(Google Analytics and our own visit tracking) to see which pages work. Read the
Cookie notice.