PUT /api/v1/tracker/shares/{shared-tracker-id}

Update an existing shared tracker configuration.

Permissions

URL Parameters

Request Body Parameters

Note: If both start_date and end_date are provided, end_date must be after start_date. When dates are set to null, date restrictions are removed.

Note: The viewer user can only change notify_* fields.

Note: The owner user can only change all fields EXCEPT notify_* fields.

Response

200 OK

<shared tracker resource>

• See Shared Tracker Resource

Error Responses

Example Request

curl -X PUT "https://api.example.com/api/v1/tracker/shares/1" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "description": "Updated January fitness tracking data",
    "include_weight": true,
    "notify_workout": true
  }'

Example Response

{
  "data": <shared tracker resource>
}

See Shared Tracker Resource for the complete response structure.

Notes

• Users can only update shared trackers where they are either the owner (user_id) or the viewer (viewer_user_id)
• Only the fields provided in the request will be updated
• The user_id and viewer_user_id fields cannot be modified
• Partial updates are supported - only include the fields you want to change
• The end_date validation rule only applies when both start_date and end_date are provided
• Setting dates to null removes date restrictions for the shared tracker