Skip to main content

Modify an existing person

Modify configuration for an existing specific person associated with your organization. This includes the list of roles for the person and whether the person is active or not.

Path Parameters
  • person_id string required

    The person ID

    Example: 903c1ff9-f2cc-435c-b242-9d8a690fcf0a
Header Parameters
  • SlashID-OrgID string required

    The organization ID

    Example: af5fbd30-7ce7-4548-8b30-4cd59cb2aba1
Request Body required

The person patch request

  • active boolean

    A flag indicating whether the person should be active or not

Responses

OK


Schema
  • meta object
  • pagination object
  • limit integer
  • offset integer
  • total_count int64
  • errors object[]
  • httpcode integer
  • message string
  • result object

    Abridged person structure

  • active boolean

    A flag indicating whether the person is active or not

  • person_id string

    The ID of the person

  • person_type string

    Possible values: [regular, anonymous]

  • region string

    Possible values: [us-iowa, europe-belgium, asia-japan, europe-england, australia-sydney]

  • handles object[]
  • type string

    Possible values: [email_address, phone_number, username]

  • value string
  • groups string[]

    Possible values: <= 100 characters, Value must match regular expression ^[A-Za-z0-9]{1}[\w\.\-]*[A-Za-z0-9]$

  • attributes object

    Attributes divided into named buckets. Bucket names are top level keys; attributes are values. Attributes consist of key-value pairs. Attribute names (keys) may be at most 70 bytes long. Attribute values must be JSON-serializable and are limited to 64KiB.

  • property name*