Production, releases and live changes
The go-live checklist and review, the releases of a live application, and the live changes that apply at once.
21 routes
{applicationId} may be the sandbox or the production id; the review and the releases are always the production record's.
The guide for this family is Changing a live application.
GET /v1/developer/applications/{applicationId}/live-changes
GET /v1/developer/applications/{applicationId}/live-changesAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/live-changes/change-requests/{changeRequestId}/withdraw
POST /v1/developer/applications/{applicationId}/live-changes/change-requests/{changeRequestId}/withdrawAuthentication- Developer console session
PUT /v1/developer/applications/{applicationId}/live-changes/redirect-uris
PUT /v1/developer/applications/{applicationId}/live-changes/redirect-urisAuthentication- Developer console session
Request body — LiveRedirectUrisDto
redirectUrisrequiredstring[]— IsArray, ArrayNotEmpty, IsString({ each: true })reasonoptionalstring— IsString, MaxLength(2000)
PUT /v1/developer/applications/{applicationId}/live-changes/scopes
PUT /v1/developer/applications/{applicationId}/live-changes/scopesAuthentication- Developer console session
Request body — LiveScopesDto
allowedClaimScopesrequiredstring[]— IsArray, ArrayNotEmpty, IsString({ each: true })allowedDataCategoriesoptionalstring[]— IsArray, IsString({ each: true })reasonoptionalstring— IsString, MaxLength(2000)
GET /v1/developer/applications/{applicationId}/production
GET /v1/developer/applications/{applicationId}/productionAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/production-review
POST /v1/developer/applications/{applicationId}/production-reviewAuthentication- Developer console session
The route the console used before D3; the same request.
The body is checked by the service rather than by a declared class, so its fields are not listed here. The guide linked above describes what it takes.
POST /v1/developer/applications/{applicationId}/production/activate
POST /v1/developer/applications/{applicationId}/production/activateAuthentication- Developer console session
The route the console used before D3; the same request.
GET /v1/developer/applications/{applicationId}/production/checklist
GET /v1/developer/applications/{applicationId}/production/checklistAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/production/review
POST /v1/developer/applications/{applicationId}/production/reviewAuthentication- Developer console session
The body is checked by the service rather than by a declared class, so its fields are not listed here. The guide linked above describes what it takes.
PUT /v1/developer/applications/{applicationId}/production/review
PUT /v1/developer/applications/{applicationId}/production/reviewAuthentication- Developer console session
The body is checked by the service rather than by a declared class, so its fields are not listed here. The guide linked above describes what it takes.
POST /v1/developer/applications/{applicationId}/production/review/withdraw
POST /v1/developer/applications/{applicationId}/production/review/withdrawAuthentication- Developer console session
GET /v1/developer/applications/{applicationId}/releases
GET /v1/developer/applications/{applicationId}/releasesAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/releases
POST /v1/developer/applications/{applicationId}/releasesAuthentication- Developer console session
A new draft, prefilled from what Production serves now.
GET /v1/developer/applications/{applicationId}/releases/{releaseId}
GET /v1/developer/applications/{applicationId}/releases/{releaseId}Authentication- Developer console session
PATCH /v1/developer/applications/{applicationId}/releases/{releaseId}
PATCH /v1/developer/applications/{applicationId}/releases/{releaseId}Authentication- Developer console session
The body is checked by the service rather than by a declared class, so its fields are not listed here. The guide linked above describes what it takes.
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/bring-over
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/bring-overAuthentication- Developer console session
A new draft, prefilled from what Production serves now.
The body is checked by the service rather than by a declared class, so its fields are not listed here. The guide linked above describes what it takes.
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/rebase
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/rebaseAuthentication- Developer console session
A new draft, prefilled from what Production serves now.
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/submit
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/submitAuthentication- Developer console session
A new draft, prefilled from what Production serves now.
The body is checked by the service rather than by a declared class, so its fields are not listed here. The guide linked above describes what it takes.
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/switch
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/switchAuthentication- Developer console session
A new draft, prefilled from what Production serves now.
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/withdraw
POST /v1/developer/applications/{applicationId}/releases/{releaseId}/withdrawAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/releases/switch-back
POST /v1/developer/applications/{applicationId}/releases/switch-backAuthentication- Developer console session
A new draft, prefilled from what Production serves now.
The body is checked by the service rather than by a declared class, so its fields are not listed here. The guide linked above describes what it takes.
What this does not do
- Responses are not listed. The API declares no response types, so this page describes what to send and who may send it. Recorded response shapes are on the guides.
- This page is generated. It was read from the API at commit
234dba22. Editing it by hand changes nothing; the next sync overwrites it.
Verified against API commit 234dba22 on 2026-10-18. The routes, scopes, checklist, events and limits on these pages are read from that export, not typed.