Changes to Get Role by Name or ID

Changed in 2 of the 5 revisions of this API.●1○11

1. Aug 8, 2025696ee83009f6○1
2. Aug 6, 202582f6f0eba091●1○10

What changed

• Aug 8, 2025696ee83009f6○1See the full diff
  • ○

    api operation id RoleNameGetRole removed and replaced with 22_get_role

    api-operation-id-removed

• Aug 6, 202582f6f0eba091●1○10See the full diff
  • ●

    removed the optional property operator from the response with the 200 status

    response-optional-property-removed

  • ○

    api operation id RoleNameGetRole was added

    api-operation-id-added

  • ○

    api tag Access Management added

    api-tag-added

  • ○

    api tag Role Management removed

    api-tag-removed

  • ○

    added the non-success response with the status 400

    response-non-success-status-added

  • ○

    removed the non-success response with the status 401

    response-non-success-status-removed

  • ○

    removed the non-success response with the status 404

    response-non-success-status-removed

  • ○

    the response property active became required for the status 200

    response-property-became-required

  • ○

    the response property email became required for the status 200

    response-property-became-required

  • ○

    the response property id became required for the status 200

    response-property-became-required

  • ○

    the response property name became required for the status 200

    response-property-became-required

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