Skip to main content
PATCH
Move a feature request to a track
Replace {your-subdomain} with your workspace’s subdomain.
Learn how to find your subdomain in Workspace subdomain.

Headers

X-Api-Key
string
required

API key. Refer to Authentication for more information.

Accept
enum<string>
default:application/json
required

Must be application/json.

Available options:
application/json

Path Parameters

id
string
required

The feature request's id (UUID) or its slug. The slug is the last segment of the feature request's admin URL, for example 120-export-roadmap-as-csv. Both are accepted.

Body

application/json
track_id
string<uuid>
required

Track to move the feature request to.

Example:

"7c1d9e52-0a4b-4f38-8e6d-93b5a2f4c107"

message
string

HTML body of the status update shown in the activity log and, when notify_all_voters is true, emailed to voters.

Example:

"<p>This shipped today.</p>"

notify_all_voters
boolean
default:false

Email the status update to every subscribed voter.

Example:

true

changelog_id
string<uuid>

Changelog to attach to the feature request.

Example:

"d4a2b6f0-9c13-4e85-a7d1-58e3c0b9f216"

operation_key
string

Retry token. See Idempotency.

Example:

"release-2026-03-move-120"

Response

The feature request was moved.

feature_request
object