Digital Product Release API

The Digital Product Release API provides endpoints to manage releases and policy compliance.

This API requires the Digital Product Release (sn_dpr) application, which is available on the ServiceNow Store. For more information, see Digital Product Release.

Parent Topic:REST API reference

Digital Product Release - GET /sn_dpr/digital_product_release/bundle/{sysId}

Retrieves release bundle details.

This endpoint can be extended to customize the fields and aggregated data returned in the response body. The default functionality of this endpoint is defined by the getReleaseBundleDetails() method in the ReleaseBundleSNC script include. To customize the functionality, override the getReleaseBundleDetails() method in the ReleaseBundle script include, which extends ReleaseBundleSNC. By default, aggregated data for enhancements, policies, release states, and task counts can be included in the response body.

To access this endpoint, the caller must have one of the following roles.

• sn_dpr_model.product_manager
• sn_dpr_model.release_admin
• sn_dpr_model.release_coordinator
• sn_dpr_model.release_user

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/bundle/{sysId}

Default URL: /api/sn_dpr/digital_product_release/bundle/{sysId}

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"aggregates": {
   "enhancementAggregate": {Object},
   "policyAggregate": {Object},
   "releaseAggregate": {Object},
   "taskAggregate": {Object}
}

"enhancementAggregate": {
   "Closed": Number,
   "Open": Number
}

"policyAggregate": {
   "Executed": Number,
   "Pending": Number
}

"releaseAggregate": {
   "Cancelled": Number,
   "Completed": Number,
   "Draft": Number,
   "In Progress": Number,
   "Pending": Number,
   "Restarting": Number,
   "Review": Number 
}

"taskAggregate": {
   "approval": Number,
   "nonApproval": Number
}

"releases": {
   "count": Number,
   "list": [Array]
}

cURL request

This example retrieves details about a specified release bundle, including aggregated data for enhancements, policies, release states, and task counts.

curl -X GET \ "https://instance.service-now.com/api/sn_dpr/v1/digital_product_release/bundle/9d0d0b4c874b1110dba83d5ebf867de2?sendAggregation=true" \
--header "Accept: application/json" \ 
--header "Authorization: Basic <base64encoded-credentials>"

Response body.

{
   "sysId": "9d0d0b4c874b1110dba83d5ebf867de2",
   "name": "Release Bundle Q4",
   "owner": "jane.doe",
   "releases": {
      "count": 2,
      "list": ["rel1", "rel2"]
   },
   "aggregates": {
      "releaseAggregate": {
         "In Progress": 1,
         "Completed": 1
      },
      "taskAggregate": {
         "approval": 3,
         "nonApproval": 5
      },
      "policyAggregate": {
         "Executed": 2,
         "Pending": 1
      },
      "enhancementAggregate": {
         "Open": 1,
         "Closed": 1
      }
   }
}

Digital Product Release - GET /sn_dpr/digital_product_release/releases/{releaseId}/policies/status

Gets policy execution details by product for the current phase of a release.

To access this endpoint, the caller must have one of the following roles.

• sn_dpr_model.product_manager
• sn_dpr_model.release_admin
• sn_dpr_model.release_coordinator
• sn_dpr_model.release_user

Before calling this endpoint, the release state must be In Progress and the current phase state must also be In Progress. You can view release information in the Digital Product Release Workspace in the Releases tab.

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/releases/{releaseId}/policies/status

Default URL: /api/sn_dpr/digital_product_release/releases/{releaseId}/policies/status

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "overallSummary": {Object},
   "products": [Array]
}

"overallSummary": {
   "compliant": Boolean,
   "compliantCount": Number,
   "currentPhase": "String",
   "nonCompliantCount": Number,
   "timestamp": "String",
   "totalCount": Number
}

"products": [
   {
      "policyExecutionDetails": [Array],
      "productId": "String",
      "productName": "String",
      "productVersion": "String",
      "summary": {Object}      
   }
]

"policyExecutionDetails": [
   {
      "executionOutput": "Check sum OK; 0 violations. Execution log id: e23-9a.",
      "lastRunAt": "2025-09-26T08:30:00Z",
      "name": "Policy Name 1",
      "policyId": "policyVersionSysId1",
      "reason": "All checks passed",
      "status": "compliant"  
   }
]

"summary": {
   "compliant": Boolean,
   "compliantCount": Number,
   "nonCompliantCount": Number,
   "totalCount": Number
}

cURL request

This example gets policy execution details for the current phase of the specified release.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/releases/d4982eeb474b621027d48b41516d4385/policies/status" \
--request GET \
--header "Accept:application/json" \
--user 'username':'password'

Response body.

{
   "result": {
      "overallSummary": {
         "compliant": false,
         "compliantCount": 3,
         "nonCompliantCount": 2,
         "totalCount": 5,
         "currentPhase": "Phase Name",
         "timestamp": "2025-09-26T09:15:00Z"
      },
      "products": [
         {
            "productId": "f8fe5fd40a0a0b9100f91d64df145295",
            "productName": "Payments Service",
            "productVersion": "v2.4.1",
            "summary": {
               "compliant": false,
               "compliantCount": 1,
               "nonCompliantCount": 1,
               "totalCount": 2
            },
            "policyExecutionDetails": [
               {
                  "name": "Policy Name 1",
                  "policyId": "f6783cc843590210ab16fc4bbcb8f223",
                  "status": "compliant",
                  "lastRunAt": "2025-09-26T08:30:00Z",
                  "executionOutput": "Check sum OK; 0 violations. Execution log id: e23-9a.",
                  "reason": "All checks passed"
               },
               {
                  "name": "Policy Name 2",
                  "policyId": "152bb04c43590210ab16fc4bbcb8f2a7",
                  "status": "non_compliant",
                  "lastRunAt": "2025-09-26T08:32:00Z",
                  "executionOutput": "Validation failed at step 3: required configuration missing.",
                  "reason": "Missing required configuration 'payments.retry_limit'"
               }
            ]
         }
      ]
   }
}

Digital Product Release - POST /sn_dpr/digital_product_release/product_enhancement

Creates an enhancement for a product or service.

To access this endpoint, the caller must have the sn_dpr_model.product_manager role.

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/product_enhancement

Default URL: /api/sn_dpr/digital_product_release/product_enhancement

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "error": Boolean,
   "sysId": "String"
}

cURL request

This example creates a product enhancement.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/product_enhancement" \
--request POST \
--header "Accept:application/json" \
--header "Content-Type:application/json" \
--data "{
   \"name\":\"Offline streaming\", 
   \"productSysId\":\"de8e9c0dfff8f2108289ffffffffff61\", 
   \"priority\":\"high\", 
   \"description\":\"Enhancement description\", 
   \"versionSysId\":\"da4b608dff7cf2108289ffffffffffc2\", 
   \"releaseSysId\":\"9a4b608dff7cf2108289ffffffffffc3\", 
   \"productFeatureSysId\":\"192d2905ff7436108289ffffffffff3f\" 
}" \
--user 'username':'password'

Response body.

{
   "result": {
      "error": false,
      "sysId": "76417985ff7436108289ffffffffff5f"
   }
}

Digital Product Release - POST /sn_dpr/digital_product_release/release

Creates a release.

A release can be created as an independent release, or as a primary release that includes child releases. This endpoint can also be used to move an existing release from the Draft state to In Progress.

To access this endpoint, the caller must have one of the following roles.

• sn_dpr_model.product_manager
• sn_dpr_model.release_admin

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/release

Default URL: /api/sn_dpr/digital_product_release/release

Supported request parameters

"autoCreateIncludedVersions": [
   { 
      "product": "String", 
      "version": "String"
   } 
]

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "error": Boolean,
   "message": "String",
   "progressId": "String",
   "releaseId": "String"
}

cURL request

This example creates a release with included versions.

curl "https://instance.service-now.com/api/sn_dpr/v1/digital_product_release/release" \ 
--request POST \ 
--header "Accept:application/json" \ 
--header "Content-Type:application/json" \ 
--data "{ 
  \"name\": \"Patch Q4\", 
  \"releaseTarget\": \"8071e5f8ff687a10509cffffffffffd9\", 
  \"releaseOwner\": \"6816f79cc0a8016401c5a33be04be441\", 
  \"releaseDescription\": \"Q4 release\", 
  \"productVersion\": \"\", 
  \"templateId\": \"c83134a4ff643a10509cffffffffffb5\", 
  \"releaseDate\": \"\", 
  \"releaseCalendar\": \"\", 
  \"includedVersions\": [ 
    \"39fd3f66ff503610509cffffffffff09\" 
  ], 
  \"productId\": \"c65c372bfb9d5610fdacfe7405efdcd7\", 
  \"autoCreateVersionName\": \"1.2\", 
  \"autoCreateIncludedVersions\": [ 
    { 
      \"product\": \"de66ea3833e966103e8361a9ed5c7b4e\", 
      \"version\": \"1.1\" 
    } 
  ] 
}" \ 
--user 'username':'password'

Response body.

{
  "result": { 
    "error": false, 
    "message": "", 
    "releaseId": "af90e98dff3c3210509cffffffffffc9", 
    "progressId": "f7902d01ffbc3210509cffffffffff7b" 
  } 
}

cURL request

This example moves an existing release from the Draft state to In Progress.

curl "https://instance.service-now.com/api/sn_dpr/v1/digital_product_release/release" \ 
--request POST \ 
--header "Accept:application/json" \ 
--header "Content-Type:application/json" \ 
--data "{ 
  \"name\": \"Q4 2025 Product Release\", 
  \"releaseTarget\": \"077e1ffb97bc4e107bc2341de053afe2\", 
  \"releaseOwner\": \"6816f79cc0a8016401c5a33be04be441\", 
  \"releaseDescription\": \"\", 
  \"productVersion\": \"0ff12581ffbc3210509cffffffffff15\", 
  \"templateId\": \"648c6ca8ffe03a10509cffffffffff11\", 
  \"releaseDate\": \"\", 
  \"releaseCalendar\": \"\", 
  \"includedVersions\": [], 
  \"productId\": \"\", 
  \"autoCreateVersionName\": \"\", 
  \"autoCreateIncludedVersions\": [], 
  \"draftReleaseId\": \"83f12581ffbc3210509cffffffffff16\" 
}" \ 
--user 'username':'password'

Response body.

{ 
  "result": { 
    "error": false, 
    "message": "", 
    "releaseId": "83f12581ffbc3210509cffffffffff16" 
  } 
}

cURL request

This example creates an independent release.

curl "https://instance.service-now.com/api/sn_dpr/v1/digital_product_release/release" \ 
--request POST \ 
--header "Accept:application/json" \ 
--header "Content-Type:application/json" \ 
--data "{ 
  \"name\": \"Q2 2026 patch\", 
  \"productVersion\": null, 
  \"releaseTarget\": \"008b84a1ffe4ba10509cffffffffff2c\", 
  \"releaseDescription\": \"\", 
  \"releaseOwner\": \"6816f79cc0a8016401c5a33be04be441\", 
  \"productId\": \"012c6d20ff203210229bffffffffff25\", 
  \"autoCreateVersionName\": \"2.4\", 
  \"templateId\": \"648c6ca8ffe03a10509cffffffffff11\", 
  \"releaseDate\": \"\", 
  \"releaseCalendar\": \"\", 
  \"isDraftRelease\": false, 
  \"validatesVersion\": true 
}" \ 
--user 'username':'password'

Response body.

{ 
  "result": { 
    "error": false, 
    "message": "", 
    "releaseId": "c6f52181ffbc3210509cffffffffffc0" 
  } 
}

Digital Product Release - POST /sn_dpr/digital_product_release/release/{releaseId}/key_date

Creates a key date for a release.

Key dates are used to track deadlines, milestones, and other important events during the release.

Before calling this endpoint, a timeline-oriented release must be created. A timeline-oriented release has fixed deadlines and follows a strict schedule, while a stage-oriented release is primarily focused on completing objectives and features rather than meeting due dates.

To access this endpoint, the caller must have one of the following roles.

• sn_dpr_model.product_manager
• sn_dpr_model.release_admin
• sn_dpr_model.release_coordinator

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/release/{releaseId}/key_date

Default URL: /api/sn_dpr/digital_product_release/release/{releaseId}/key_date

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "error": Boolean,
   "keyDateSysId": "String",
   "message": "String"
}

cURL request

This example creates a project launch date for a specified release.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release/eb7dd11d97b402107bc2341de053af34/key_date" \
--request POST \
--header "Accept:application/json" \
--header "Content-Type:application/json" \
--data "{ 
    \"name\": \"Project Launch\", 
    \"type\": \"milestone\", 
    \"dueDate\": \"2025-11-01\", 
    \"state\": \"upcoming\", 
    \"description\": \"Launching the new project phase.\", 
    \"assignedTo\": \"62826bf03710200044e0bfc8bcbe5df1\" 
}" \
--user 'username':'password'

Response body.

{
   "result": {
      "error": false,
      "message": "Release key date created successfully",
      "keyDateSysId": "eb0b0905ff7036108289ffffffffff6d"
   }
}

Digital Product Release - POST /sn_dpr/digital_product_release/release/{releaseId}/policies/run

Executes mapped policies for the current phase of a release.

To access this endpoint, the caller must have the sn_dpr_model.product_manager role.

Before calling this endpoint, the release state must be In Progress and the current phase state must also be In Progress. You can view release information in the Digital Product Release Workspace in the Releases tab.

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/release/{releaseId}/policies/run

Default URL: /api/sn_dpr/digital_product_release/release/{releaseId}/policies/run

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "error": Boolean,
   "errorCode": "String",
   "message": "String",
   "policyExecutionScheduled": Boolean
}

cURL request

This example executes the mapped policies for the current phase of the specified release.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release/d4982eeb474b621027d48b41516d4385/policies/run" \
--request POST \
--header "Accept:application/json" \
--user 'username':'password'

Response body.

{
   "result": {
      "error": false,
      "errorCode": "",
      "message": "Policy execution scheduled.",
      "policyExecutionScheduled": true
   }
}

Digital Product Release - POST /sn_dpr/digital_product_release/release/{releaseId}/related_task

Adds related tasks to a release.

You can view release information in the Digital Product Release Workspace in the Releases tab. Related tasks for a release are shown in the Release Scope section of a release record.

Important: Before calling this endpoint, there must be existing task records that can be added as related tasks for the release. The records must be in tables that extend the Task [task] table, but not in the Task table itself. In the sn_dpr_model.release_related_task_types system property, list the tables that contain your task records.

To access this endpoint, the caller must have one of the following roles.

• sn_dpr_model.product_manager
• sn_dpr_model.release_admin

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/release/{releaseId}/related_task

Default URL: /api/sn_dpr/digital_product_release/release/{releaseId}/related_task

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "error": Boolean,
   "message": "String"
}

cURL request

This example adds two related tasks to a release.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release/eb7dd11d97b402107bc2341de053af34/related_task" \
--request POST \
--header "Accept:application/json" \
--header "Content-Type:application/json" \
--data "{\"taskIds\": [\"36836028532023004247ddeeff7b12f1\", \"bc84b11dff5c32108289ffffffffff12\"]}" \
--user 'username':'password'

Response body.

{
   "result": {
      "error": false,
      "message": "Successfully created the mappings between the release and all the tasks."
   }
}

Digital Product Release - POST /sn_dpr/digital_product_release/release_calendar

Creates a release calendar.

To access this endpoint, the caller must have the sn_dpr_model.release_calendar_admin role.

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/release_calendar

Default URL: /api/sn_dpr/digital_product_release/release_calendar

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "error": Boolean,
   "message": "String",
   "releaseCalendarId": "String"
}

cURL request

This example creates a release calendar.

curl 'https://instance.service-now.com/api/sn_dpr/v1/digital_product_release/release_calendar' \ 
--request POST \
--header 'Accept:application/json' \
--header 'Content-Type: application/json' \ 
--header 'Authorization: Basic <base64encoded-credentials>' \ 
--data '{ 
    "name": "Q1 2025 Release Calendar123", 
    "releaseAdmin": "dc6770ae3b97a210532fb50f23e45a33", 
    "description": "Calendar for Q1 releases" 
}'

Response body.

{
   "result": {
      "error": false,
      "message": "",
      "releaseCalendarId": "5f6702c13bbc3a50532fb50f23e45a2b"
   }
}

Digital Product Release - POST /sn_dpr/digital_product_release/release_id/{releaseId}/complete_phase

Completes the current phase of a release.

Note: The current phase is only set to Completed if all policies for the phase are compliant.

To access this endpoint, the caller must have one of the following roles.

• sn_dpr_model.product_manager
• sn_dpr_model.release_admin
• sn_dpr_model.release_coordinator

Before calling this endpoint, the release state must be In Progress and the current phase state must also be In Progress. You can view release information in the Digital Product Release Workspace in the Releases tab.

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/release_id/{releaseId}/complete_phase

Default URL: /api/sn_dpr/digital_product_release/release_id/{releaseId}/complete_phase

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "message": "String",
   "phaseSysId": "String",
   "status": "String",
}

"result": {
   "error": Boolean,
   "message": "String"
}

cURL request

This example completes the current phase of the specified release.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release_id/d4982eeb474b621027d48b41516d4385/complete_phase" \
--request POST \
--header "Accept:application/json" \
--user 'username':'password'

Response body.

{
  "result": {
    "status": "success",
    "message": "Release phase is marked as complete",
    "phaseSysId": "2498222f474b621027d48b41516d4342"
  }
}

cURL request

This example shows an error response when an invalid release sys_id is provided.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release_id/a/complete_phase" \
--request POST \
--header "Accept:application/json" \
--user 'username':'password'

Error response.

{
  "result": {
    "error": true,
    "message": "Release ID is invalid"
  }
}

Digital Product Release - POST /sn_dpr/digital_product_release/release_target

Creates a release readiness target or a set of recurring release readiness targets.

To access this endpoint, the caller must have one of the following roles.

• sn_dpr_model.product_manager
• sn_dpr_model.release_admin

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/release_target

Default URL: /api/sn_dpr/digital_product_release/release_target

Supported request parameters

"repeats": {
   "daysOfWeek": Number,
   "every": Number,
   "type": "String"
}

"repeats": {
   "every": 2,
   "type": "weekly"
}

"targetsWithOverlappingScheduleDetails": [ 
   { 
      "active": Boolean, 
      "date": "String" 
   }
]

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "count": Number,
   "error": Boolean,
   "message": "String"
}

cURL request

This example creates a set of four release readiness targets, with a target recurring every week on Friday.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release_target" \ 
--request POST \ 
--header "Accept:application/json" \ 
--header "Content-Type:application/json" \ 
--data "{ 
  \"name\": \"Weekly Friday patch\", 
  \"releaseAdmin\": \"6816f79cc0a8016401c5a33be04be441\", 
  \"isRecurring\": true, 
  \"description\": \"\", 
  \"startDate\": \"2025-10-24\", 
  \"releaseCalendar\": \"d3d1f3b4ff60ba10509cffffffffffa8\", 
  \"endDate\": \"2025-11-19\", 
  \"repeats\": { 
    \"type\": \"weekly\", 
    \"every\": 1, 
    \"daysOfWeek\": 5 
  }, 
  \"scheduleSysId\": \"b862d589ff3c3210509cffffffffff97\", 
  \"targetsWithOverlappingScheduleDetails\": [ 
    { 
      \"active\": true, 
      \"date\": \"2025-10-24\" 
    }, 
    { 
      \"active\": true, 
      \"date\": \"2025-10-31\" 
    }, 
    { 
      \"active\": true, 
      \"date\": \"2025-11-07\" 
    }, 
    { 
      \"active\": true, 
      \"date\": \"2025-11-14\" 
    } 
  ] 
}" \ 
--user 'username':'password'

Response body.

{
  "result": {
    "error": false,
    "message": "",
    "count": 4
  }
}

cURL request

This example creates a release readiness target for a specified date.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release_target" \ 
--request POST \ 
--header "Accept:application/json" \ 
--header "Content-Type:application/json" \ 
--data "{ 
  \"name\": \"Fourth Thursday patch\", 
  \"releaseAdmin\": \"6816f79cc0a8016401c5a33be04be441\", 
  \"isRecurring\": false, 
  \"description\": \"Last Thursday of October\", 
  \"startDate\": \"2025-10-30\", 
  \"releaseCalendar\": \"d3d1f3b4ff60ba10509cffffffffffa8\" 
}" \ 
--user 'username':'password' 

Response body.

{
  "result": {
    "error": false,
    "message": "",
    "count": 1
  }
}

Digital Product Release - PUT /sn_dpr/digital_product_release/release/{sysId}/retarget

Changes the readiness target for a release.

The new readiness target can be an existing readiness target that is already defined, or an out-of-band date (a one-time readiness target not tied to the standard release calendar). To set an out-of-band date, the sn_dpr.out_of_band_release_allowed system property must be set to true.

The release phase duration is adjusted to reflect the new readiness target.

Before calling this endpoint, the release state must be In Progress or Pending.

To access this endpoint, the caller must have one of the following roles.

• sn_dpr_model.product_manager
• sn_dpr_model.release_admin

URL format

Versioned URL: /api/sn_dpr/{api_version}/digital_product_release/release/{sysId}/retarget

Default URL: /api/sn_dpr/digital_product_release/release/{sysId}/retarget

Supported request parameters

Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.

Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.

Response body parameters (JSON)

"result": {
   "error": Boolean,
   "message": "String"
}

cURL request

This example updates the release readiness target using an existing readiness target.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release/9b2e7ec9476c8e105b8e0dcfe16d43d4/retarget" \
--request PUT \
--header "Accept:application/json" \
--header "Content-Type:application/json" \
--data "{
   \"releaseTarget\": \"3f6668e95427fd10f877ac7ac399daa6\"
}" \
--user 'username':'password'

Response body.

{
  "result": {
    "error": false,
    "message": ""
  }
}

cURL request

This example updates the release readiness target using an out-of-band readiness target.

curl "https://instance.service-now.com/api/sn_dpr/digital_product_release/release/9b2e7ec9476c8e105b8e0dcfe16d43d4/retarget" \
--request PUT \
--header "Accept:application/json" \
--header "Content-Type:application/json" \
--data "{
   \"outOfBand\": true,
   \"releaseCalendar\": \"fcb2eaa09f4302105c534d837a0a1c2b\",
   \"releaseDate\": \"2026-10-23\"
}" \
--user 'username':'password'

Response body.

{
  "result": {
    "error": false,
    "message": ""
  }
}