Update roadmap item
Update the status and/or release version, date and notes of an existing roadmap item (it never creates one). The roadmap is global to the instance, so the key needs instance access. Fires the roadmap webhook and emails the submitter as the platform they submitted on. A request that changes nothing sends neither. Optional source is echoed in the webhook so the caller can ignore its own change. Release fields are only accepted when the status is released.
Authentication: API key via X-API-Key header (or Authorization: Bearer). Permissions: User API key with instance access Rate limit: api_admin_write — 20 requests/min per API user.
Authorizations
Preferred. API key value directly.
Query Parameters
Roadmap item id.
"YOUR_ID"
exploring | planned | in_progress | beta | released.
"YOUR_STATUS"
For example v2.4.0. Only with status released.
"YOUR_RELEASEVERSION"
ISO date, for example 2026-10-15. Only with status released.
"YOUR_RELEASEDATE"
Release notes. Only with status released.
"YOUR_RELEASENOTES"
Who is calling (a-z, 0-9, - and _, up to 32). Echoed as data.source in the webhook; defaults to api.
"YOUR_SOURCE"
Body
Roadmap item id.
"YOUR_ID"
exploring | planned | in_progress | beta | released.
"YOUR_STATUS"
For example v2.4.0. Only with status released.
"YOUR_RELEASEVERSION"
ISO date, for example 2026-10-15. Only with status released.
"YOUR_RELEASEDATE"
Release notes. Only with status released.
"YOUR_RELEASENOTES"
Who is calling (a-z, 0-9, - and _, up to 32). Echoed as data.source in the webhook; defaults to api.
"YOUR_SOURCE"