Create user

POST 
/scim/v2/Users

Creates an SCIM user with optional employer organization membership.

The request body must contain valid SCIM 2.0 user data. If you provide employer organization, the user is added to the specified organization with the specified roles.

Request

application/scim+json

Body

required

schemas string[]required
id string

Encrypted account ID (external format).

externalId string

External identifier for the user.

userName string

Unique username for the user.

name

object

SCIM Name complex type

formatted string

Full name.

familyName string

Family name. Also known as last name.

givenName string

Given name. Also known as first name.

middleName string

Middle name.

honorificPrefix string

Honorific prefix, such as Mr. or Dr.

honorificSuffix string

Honorific suffix, such as Jr. or Sr.

displayName string

Display name for the user.

emails

object[]

Array [

value emailrequired

Email address.

type string

Possible values: [work, home, other]

Email type.

primary boolean

Indicates whether this email is the primary email.

]

active boolean

Indicates whether the user account is active.

meta

object

SCIM Meta complex type

resourceType string

Resource type.

created date-time

Creation timestamp.

lastModified date-time

Last modification timestamp.

location uri

Resource location URL.

version string

Resource version/ETag.

urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg

object

Indeed-specific employer organization extension

id string

Employer organization ID.

roles string[]

Possible values: [admin]

User roles within the employer organization:

• admin: Organization administrator
• Empty array or null: Basic member

Responses

201

User created successfully

Response Headers

• Location

  string

  URL of the created user resource.

• ETag

  string

  Entity tag for the created resource.

application/scim+json

Schema

Schema

schemas string[]required
id string

Encrypted account ID (external format).

externalId string

External identifier for the user.

userName string

Unique username for the user.

name

object

SCIM Name complex type

formatted string

Full name.

familyName string

Family name. Also known as last name.

givenName string

Given name. Also known as first name.

middleName string

Middle name.

honorificPrefix string

Honorific prefix, such as Mr. or Dr.

honorificSuffix string

Honorific suffix, such as Jr. or Sr.

displayName string

Display name for the user.

emails

object[]

Array [

value emailrequired

Email address.

type string

Possible values: [work, home, other]

Email type.

primary boolean

Indicates whether this email is the primary email.

]

active boolean

Indicates whether the user account is active.

meta

object

SCIM Meta complex type

resourceType string

Resource type.

created date-time

Creation timestamp.

lastModified date-time

Last modification timestamp.

location uri

Resource location URL.

version string

Resource version/ETag.

urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg

object

Indeed-specific employer organization extension

id string

Employer organization ID.

roles string[]

Possible values: [admin]

User roles within the employer organization:

• admin: Organization administrator
• Empty array or null: Basic member

Example (from schema)

{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:User",
    "urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg"
  ],
  "id": "encrypted-account-key-123",
  "externalId": "ext-user-123",
  "userName": "john.doe@example.com",
  "name": {
    "formatted": "Mr. John Q. Doe",
    "familyName": "Doe",
    "givenName": "John",
    "middleName": "Q",
    "honorificPrefix": "Mr.",
    "honorificSuffix": "Jr."
  },
  "displayName": "John Doe",
  "emails": [
    {
      "value": "john.doe@example.com",
      "type": "work",
      "primary": true
    }
  ],
  "active": true,
  "meta": {
    "resourceType": "User",
    "created": "2023-01-01T00:00:00Z",
    "lastModified": "2023-01-01T00:00:00Z",
    "location": "https://api.indeed.com/scim/v2/Users/encrypted-account-key-123",
    "version": "\"W/1\""
  },
  "urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg": {
    "id": "org-123",
    "roles": [
      "admin"
    ]
  }
}

createdUser

{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:User",
    "urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg"
  ],
  "id": "encrypted-account-key-123",
  "externalId": "ext-user-123",
  "userName": "john.doe@example.com",
  "name": {
    "formatted": "John Doe",
    "familyName": "Doe",
    "givenName": "John"
  },
  "displayName": "John Doe",
  "emails": [
    {
      "value": "john.doe@example.com",
      "type": "work",
      "primary": true
    }
  ],
  "active": true,
  "meta": {
    "resourceType": "User",
    "created": "2023-01-01T00:00:00Z",
    "lastModified": "2023-01-01T12:00:00Z",
    "location": "https://api.indeed.com/scim/v2/Users/encrypted-account-key-123",
    "version": "\"W/2\""
  },
  "urn:ietf:params:scim:schemas:extension:indeed:2.0:EmployerOrg": {
    "id": "org-123",
    "roles": [
      "admin"
    ]
  }
}

400

Bad Request - Invalid request format or parameters

application/scim+json

Schema

Schema

schemas string[]required
status stringrequired

HTTP status code as string.

scimType string

Possible values: [invalidFilter, tooMany, uniqueness, mutability, invalidSyntax, invalidPath, noTarget, invalidValue, invalidVers, sensitive]

SCIM error type.

detail string

Human-readable error description.

Example (from schema)

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "400",
  "scimType": "invalidFilter",
  "detail": "Invalid filter: No filter provided"
}

invalidFilter

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "400",
  "scimType": "invalidFilter",
  "detail": "Invalid filter: No filter provided"
}

invalidUser

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "400",
  "scimType": "invalidValue",
  "detail": "Invalid SCIM user data"
}

401

Unauthorized - Invalid or missing authentication

application/scim+json

Schema

Schema

schemas string[]required
status stringrequired

HTTP status code as string.

scimType string

Possible values: [invalidFilter, tooMany, uniqueness, mutability, invalidSyntax, invalidPath, noTarget, invalidValue, invalidVers, sensitive]

SCIM error type.

detail string

Human-readable error description.

Example (from schema)

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "400",
  "scimType": "invalidFilter",
  "detail": "Invalid filter: No filter provided"
}

Example

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "401",
  "detail": "Authentication required"
}

403

Forbidden - Insufficient permissions

application/scim+json

Schema

Schema

schemas string[]required
status stringrequired

HTTP status code as string.

scimType string

Possible values: [invalidFilter, tooMany, uniqueness, mutability, invalidSyntax, invalidPath, noTarget, invalidValue, invalidVers, sensitive]

SCIM error type.

detail string

Human-readable error description.

Example (from schema)

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "400",
  "scimType": "invalidFilter",
  "detail": "Invalid filter: No filter provided"
}

Example

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "403",
  "detail": "Insufficient permissions"
}

409

Conflict - Resource already exists

application/scim+json

Schema

Schema

schemas string[]required
status stringrequired

HTTP status code as string.

scimType string

Possible values: [invalidFilter, tooMany, uniqueness, mutability, invalidSyntax, invalidPath, noTarget, invalidValue, invalidVers, sensitive]

SCIM error type.

detail string

Human-readable error description.

Example (from schema)

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "400",
  "scimType": "invalidFilter",
  "detail": "Invalid filter: No filter provided"
}

Example

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "409",
  "scimType": "uniqueness",
  "detail": "User already exists"
}

500

Internal Server Error

application/scim+json

Schema

Schema

schemas string[]required
status stringrequired

HTTP status code as string.

scimType string

Possible values: [invalidFilter, tooMany, uniqueness, mutability, invalidSyntax, invalidPath, noTarget, invalidValue, invalidVers, sensitive]

SCIM error type.

detail string

Human-readable error description.

Example (from schema)

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "400",
  "scimType": "invalidFilter",
  "detail": "Invalid filter: No filter provided"
}

Example

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:Error"
  ],
  "status": "500",
  "detail": "An unexpected error occurred"
}

Loading...

 

Was this page helpful?