Create new person
Create a new person linked to your organization. The request must contain at least one handle for the person (email address, phone number, or username). Optionally, you can specify a list of roles, a geographical region and attributes. Attributes are a map from attribute bucket names to key-value pairs. If a person with the specified handles already exists, an error will be returned. If the region is not specified, the person will be created in the region closest to the region of your backend. If you explicitly specify the region and a person with the provided handle already exists in a different region, this endpoint will return an error. A person's region association is eventually consistent between regions. Because of that, creating a person between regions within the time frame of data replication can result in a person being created in multiple regions. You can learn more on the Cross-region replication model page.
Header Parameters
- SlashID-OrgID string required
The organization ID
Example: af5fbd30-7ce7-4548-8b30-4cd59cb2aba1
- application/json
Request Body required
The person creation request
- active boolean
A flag indicating whether the person should be active or not
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*
handles object[]
the list of handles for the user
type string requiredPossible values: [
email_address
,phone_number
,username
]value string required- groups string[]
Possible values:
<= 100 characters
, Value must match regular expression^[A-Za-z0-9]{1}[\w\.\-]*[A-Za-z0-9]$
A list of group names to assign the person to. Previous groups are overwritten. Groups must already exist.
- region string
Possible values: [
us-iowa
,europe-belgium
,asia-japan
,europe-england
,australia-sydney
] - credentials object[]
- 201
- 400
- 402
- 404
- 409
Created
- application/json
- Schema
- Example (from schema)
Schema
meta object
pagination object
limit integeroffset integertotal_count int64errors object[]
httpcode integermessage stringresult object
Abridged person structure
active booleanA flag indicating whether the person is active or not
person_id stringThe ID of the person
person_type stringPossible values: [
regular
,anonymous
]region stringPossible values: [
us-iowa
,europe-belgium
,asia-japan
,europe-england
,australia-sydney
]handles object[]
type stringPossible values: [
email_address
,phone_number
,username
]value stringgroups 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*
{
"meta": {
"pagination": {
"limit": 0,
"offset": 0,
"total_count": 0
}
},
"errors": [
{
"httpcode": 0,
"message": "string"
}
],
"result": {
"active": true,
"person_id": "string",
"person_type": "regular",
"region": "us-iowa",
"handles": [
{
"type": "email_address",
"value": "string"
}
],
"groups": [
"string"
],
"attributes": {}
}
}
Bad Request
- application/json
- Schema
- Example (from schema)
Schema
meta object
pagination object
limit integeroffset integertotal_count int64errors object[]
httpcode integermessage string
{
"meta": {
"pagination": {
"limit": 0,
"offset": 0,
"total_count": 0
}
},
"errors": [
{
"httpcode": 0,
"message": "string"
}
]
}
Pricing Tier Violation - operation violated the limits specified in its pricing tier.
- application/json
- Schema
- Example (from schema)
Schema
meta object
pagination object
limit integeroffset integertotal_count int64errors object[]
httpcode integermessage string
{
"meta": {
"pagination": {
"limit": 0,
"offset": 0,
"total_count": 0
}
},
"errors": [
{
"httpcode": 0,
"message": "string"
}
]
}
Not Found
- application/json
- Schema
- Example (from schema)
Schema
meta object
pagination object
limit integeroffset integertotal_count int64errors object[]
httpcode integermessage string
{
"meta": {
"pagination": {
"limit": 0,
"offset": 0,
"total_count": 0
}
},
"errors": [
{
"httpcode": 0,
"message": "string"
}
]
}
Conflict
- application/json
- Schema
- Example (from schema)
Schema
meta object
pagination object
limit integeroffset integertotal_count int64errors object[]
httpcode integermessage string
{
"meta": {
"pagination": {
"limit": 0,
"offset": 0,
"total_count": 0
}
},
"errors": [
{
"httpcode": 0,
"message": "string"
}
]
}