---
sourceDocument: Brazil API Reference
sourceDocumentLink: https://www.servicenow.com/docs/r/api-reference

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Reassign Assessment API

# Reassign Assessment API {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read  
The Reassign Assessment API provides an endpoint to reassign an assessment instance to a different user.
The Reassign Assessment API runs in the sn_smart_asmt namespace. This API is offered by default with the base system.

Use this API to transfer assessment ownership when you need to change which user is responsible for completing an in-progress assessment. This is useful when assessments are initially assigned incorrectly, when an employee changes roles, or when you need to delegate assessment completion to a more appropriate team member.

## Common use cases {#reassign-assessment-api__section_use_cases}

* Transferring assessment responsibility when an employee changes roles or leaves the organization
* Correcting an incorrectly assigned assessment
* Delegating assessment completion to a more appropriate team member
{#reassign-assessment-api__ul_fdv_4sh_zjc}

## Requirements {#reassign-assessment-api__section_l5w_ymh_zjc}

The Reassign Assessment API requires the following roles to access it:

* Users with the sn_smart_asmt.actor role who have been assigned the assessment (only the primary owner)
* Assessment requestors with the sn_smart_asmt.assessment_reader role
* Users with the sn_smart_asmt.assessment_admin role
{#reassign-assessment-api__ul_zqh_2dd_1kc}

## Important constraints {#reassign-assessment-api__section_constraints}

* The assessment must be in the Open state to be reassigned. Assessments in other states can't be reassigned using this endpoint.
* The requesting user must have write access to the assessment's persona assignment record to perform the reassignment.
* An assessment can't be reassigned to the user it's currently assigned to.

## Reassign Assessment - PATCH /{userId} {#ariaid-title2}

Reassigns an assessment instance to a different user. Use this endpoint when you need to transfer ownership of an in-progress assessment from the current assignee to another user.
The assessment must be in the "Open" state to be reassigned. This endpoint updates the primary owner on the assessment instance persona record, effectively changing who is responsible for completing the assessment.  
Common use cases include:

* Transferring assessment responsibility when an employee changes roles or leaves the organization.
* Correcting an incorrectly assigned assessment.
* Delegating assessment completion to a more appropriate team member.

{#reassignassessment-PATCH-userId__ul_ryp_znh_zjc}  
Note:  
The requesting user must have write access to the assessment's persona assignment record to perform the reassignment.

### URL format

Versioned URL: PATCH /api/sn_smart_asmt/{api_version}/instance/asmt/{asmtInstanceId}/user/{userId}

Default URL: PATCH /api/sn_smart_asmt/instance/asmt/{asmtInstanceId}/user/{userId}

### Supported request parameters

{#reassignassessment-PATCH-userId__entry__2}{#reassignassessment-PATCH-userId__version-not_optional-RESTAPI}

| Name | Description |
|-|-|
| api_version | Optional. Version of the endpoint to access. For example, <kbd class="ph userinput">v1</kbd> or <kbd class="ph userinput">v2</kbd>. Only specify this value to use an endpoint version other than the latest. Data type: String |
| asmtInstanceId | Required. Sys_id of the assessment instance to reassign. Table: Assessment Instance \[sn_smart_asmt_instance\] Maximum length: 32 Data type: String |
| userId | Required. Sys_id of the user to whom the assessment will be reassigned. Table: User \[sys_user\] Maximum length: 32 Data type: String |
[Table 1. Path parameters]

{#reassignassessment-PATCH-userId__entry__10}

| Name | Description |
|-|-|
| None |   |
[Table 2. Query parameters]

{#reassignassessment-PATCH-userId__entry__14}

| Name | Description |
|-|-|
| None |   |
[Table 3. Request body parameters (XML or JSON)]

### 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](https://www.servicenow.com/docs/TSHwMH5MZNTdV2wXSUhSiw "REST (REpresentational State Transfer) is a simple stateless architecture that provides standards between computer systems on the web, making it easier for them to communicate with each other.").
{#reassignassessment-PATCH-userId__entry__18}

| Header | Description |
|-|-|
| Accept | Data format of the response body. Supported values: application/json, application/xml, text/xml. Default: application/json. |
| Authorization | Authentication credentials. Use Basic authentication with base64-encoded username:password, or an OAuth 2.0 bearer token. |
| Content-Type | Not required for this endpoint as there is no request body, but if provided, supported values are: application/json, application/xml, text/xml. |
[Table 4. Request headers]

{#reassignassessment-PATCH-userId__entry__26}

| Header | Description |
|-|-|
| Content-Type | Data format of the response body. Matches the Accept header value or defaults to application/json. |
| X-Is-Logged-In | Flag that indicates whether the requesting user is logged in. Possible values: true, false. |
| X-Transaction-ID | Unique identifier for the transaction, useful for debugging and support requests. |
[Table 5. Response 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](https://www.servicenow.com/docs/TSHwMH5MZNTdV2wXSUhSiw "REST (REpresentational State Transfer) is a simple stateless architecture that provides standards between computer systems on the web, making it easier for them to communicate with each other.").
{#reassignassessment-PATCH-userId__entry__34}

| Status code | Description |
|-|-|
| 200 | Success. The assessment was successfully reassigned to the specified user. No response body is returned. |
| 400 | Bad Request. The request is missing required path parameters. Possible error messages: * `Assessment id is not passed.` * `User id is not passed.` {#reassignassessment-PATCH-userId__ul_xbw_wph_zjc} |
| 403 | Forbidden. The requesting user doesn't have authorization to reassign this assessment. This occurs when the user lacks write access to the assessment's persona assignment record. Error message: `User not authorized to reassign.` |
| 404 | Not Found. The specified resource doesn't exist. Possible error messages: * `Assessment instance not found.` * `User not found.` * `Persona assignment record for assessor is not available for the assessment.` {#reassignassessment-PATCH-userId__ul_iv4_cqh_zjc} |
| 406 | Not acceptable. The reassignment can't be completed due to business rule constraints. Possible error messages: * `Assessment can't be reassigned as it's not in {state_name} state` - Assessment must be in Open state. * `Assessment can't be reassigned as it's already assigned to the current user` * `Unable to reassign the assessment` - Generic failure during update. {#reassignassessment-PATCH-userId__ul_xy2_lph_zjc} |
[Table 6. Status codes]

### Response body parameters (JSON or XML)

{#reassignassessment-PATCH-userId__entry__46}

| Name | Description |
|-|-|
| Object | Return object containing results of the reassignment. { "error": {Object}, "status": "String" } |
| error | Object containing error details. Data type: Object "error": { "detail": "String", "message": "String" } |
| error.message | Human-readable description of the error that occurred. Examples: * `Assessment ID isn't passed.` * `User not authorized to reassign.` * `Assessment instance not found.` {#reassignassessment-PATCH-userId__ul_ubx_mqh_zjc} Data type: String |
| error.detail | Additional details about the error, if available. May be empty. Data type: String |
| status | Indicates the outcome of the request. Possible values: `"failure"` (when an error occurs). Successful responses (HTTP 200) return an empty body with no status field. |
[ ]

### cURL request

This PATCH example reassigns the assessment with ID `4d812fed47f8835060b5e65d416d431a` to the user with ID `62826bf03710200044e0bfc8bcbe5df1`.

    curl "https://testsae.service-now.com/api/sn_smart_asmt/instance/asmt/4d812fed47f8835060b5e65d416d431a/user/62826bf03710200044e0bfc8bcbe5df1" \
    --request PATCH \
    --header "Accept:application/json" \
    --user 'admin':'admin'

Response:

    {
      "error": {
        "message": "Assessment can't be reassigned as it is already assigned to the current user",
        "detail": ""
      },
      "status": "failure"
    }