Sign in
Impersonation Settings

Update Impersonation Settings

Updates Impersonation Settings.

patch/v3/organizations/impersonation

Request body

enabledboolean

Indicates if user impersonation is allowed for the organization.

Example request

{
  "enabled": true
}

Response

Response for Update Impersonation Settings endpoint

enabledboolean

The organization has user impersonation enabled.

Example response

{
  "enabled": true
}

Changes

Changed in 3 of the 75 revisions of this API.1111

  • 845120e19d451See the full diff
    • ▲

      the request property enabled became not nullable

      request-property-became-not-nullable

  • 8ab3ec3ed3011See the full diff
    • ●

      added the new type enum value to the allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterStandard]/rule response property for the response status 400

      response-property-enum-value-added

  • 3c0154b2053a101See the full diff
    • ▲

      the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterChoiceItem]/source became nullable for the status 400

      response-property-became-nullable

    • ▲

      the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterDependentItem]/source became nullable for the status 400

      response-property-became-nullable

    • ▲

      the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterMaximumLength]/source became nullable for the status 400

      response-property-became-nullable

    • ▲

      the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterMinimumLength]/source became nullable for the status 400

      response-property-became-nullable

    • ▲

      the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterStandard]/source became nullable for the status 400

      response-property-became-nullable

    • ▲

      the response property detail became nullable for the status 403

      response-property-became-nullable

    • ▲

      the response property enabled became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property instance became nullable for the status 403

      response-property-became-nullable

    • ▲

      the response property status became nullable for the status 403

      response-property-became-nullable

    • ▲

      the response property title became nullable for the status 403

      response-property-became-nullable

    • ○

      the request property enabled became nullable

      request-property-became-nullable

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog