SCIM2 Discovery

SCIM 2.0 discovery endpoints for ServiceProviderConfig, Schemas, and ResourceTypes. These endpoints allow clients to discover SCIM server capabilities.

Learn more about SCIM 2.0

Get SCIM service provider configuration

get

Returns the SCIM 2.0 Service Provider Configuration, which describes the SCIM specification features supported by this service provider.

SCIM 2.0 Compliance

This endpoint follows the SCIM 2.0 specification for service provider configuration discovery.

Supported Features

• filter: Filtering is supported (maxResults: 100)

• patch: PATCH operations are supported

• bulk: Bulk operations are not supported

• changePassword: Password changes are not supported

• sort: Sorting is not supported

• etag: ETags are not supported

---

Important Notes!

• This endpoint does not require authentication

• Use this endpoint to discover server capabilities before making other requests

Authorizations

bearerAuth

AuthorizationstringRequired

API authentication using Bearer tokens. Include your API token in the Authorization header: Authorization: Bearer <your-api-token>

Tokens can be obtained from the Opsera platform's API token management interface.

Responses

200

Successfully retrieved service provider configuration

application/scim+json

schemasstring[]OptionalExample: ["urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig"]

get

/api/v2/scim/v2/ServiceProviderConfig

HTTPcURLJavaScriptPython

GET /api/v2/scim/v2/ServiceProviderConfig HTTP/1.1
Host: api.[organization].opsera.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

200

Successfully retrieved service provider configuration

{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig"
  ],
  "patch": {
    "supported": false
  },
  "bulk": {
    "supported": false,
    "maxOperations": 100,
    "maxPayloadSize": 1048576
  },
  "filter": {
    "supported": true,
    "maxResults": 100
  },
  "changePassword": {
    "supported": false
  },
  "sort": {
    "supported": false
  },
  "etag": {
    "supported": false
  },
  "xmlDataFormat": {
    "supported": false
  },
  "authenticationSchemes": [
    {
      "name": "OAuth Bearer Token",
      "description": "Authentication using bearer tokens",
      "type": "oauthbearertoken",
      "primary": true,
      "specUrl": "https://tools.ietf.org/html/rfc6749"
    }
  ]
}

Get all SCIM schemas

get

Returns all SCIM 2.0 schemas supported by this service provider.

SCIM 2.0 Compliance

This endpoint follows the SCIM 2.0 specification for schema discovery.

Supported Schemas

• urn:ietf:params:scim:schemas:core:2.0:User - User resource schema

• urn:ietf:params:scim:schemas:core:2.0:Group - Group resource schema

---

Important Notes!

• Use this endpoint to discover available resource schemas

• Each schema describes the attributes available for that resource type

Authorizations

bearerAuth

AuthorizationstringRequired

API authentication using Bearer tokens. Include your API token in the Authorization header: Authorization: Bearer <your-api-token>

Tokens can be obtained from the Opsera platform's API token management interface.

Responses

200

Successfully retrieved schemas

application/scim+json

schemasstring[]OptionalExample: ["urn:ietf:params:scim:schemas:core:2.0:Schema"]

totalResultsintegerOptionalExample: 2

get

/api/v2/scim/v2/Schemas

HTTPcURLJavaScriptPython

GET /api/v2/scim/v2/Schemas HTTP/1.1
Host: api.[organization].opsera.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

200

Successfully retrieved schemas

{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:Schema"
  ],
  "totalResults": 2,
  "Resources": [
    {
      "id": "text",
      "name": "text",
      "description": "text",
      "attributes": [
        {}
      ]
    }
  ]
}

Get a specific SCIM schema

get

Returns a specific SCIM 2.0 schema by its identifier.

SCIM 2.0 Compliance

This endpoint follows the SCIM 2.0 specification for schema discovery.

Available Schema IDs

• urn:ietf:params:scim:schemas:core:2.0:User - User resource schema

• urn:ietf:params:scim:schemas:core:2.0:Group - Group resource schema

Authorizations

bearerAuth

AuthorizationstringRequired

API authentication using Bearer tokens. Include your API token in the Authorization header: Authorization: Bearer <your-api-token>

Tokens can be obtained from the Opsera platform's API token management interface.

Path parameters

idstringRequired

The schema identifier (URN)

Example: urn:ietf:params:scim:schemas:core:2.0:User

Responses

200

Successfully retrieved schema

application/scim+json

idstringOptionalExample: urn:ietf:params:scim:schemas:core:2.0:User

namestringOptionalExample: User

descriptionstringOptionalExample: SCIM core resource for representing users

attributesobject[]Optional

404

Schema not found

application/scim+json

get

/api/v2/scim/v2/Schemas/{id}

HTTPcURLJavaScriptPython

GET /api/v2/scim/v2/Schemas/{id} HTTP/1.1
Host: api.[organization].opsera.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

{
  "id": "urn:ietf:params:scim:schemas:core:2.0:User",
  "name": "User",
  "description": "SCIM core resource for representing users",
  "attributes": [
    {}
  ]
}

Get all SCIM resource types

get

Returns all SCIM 2.0 resource types supported by this service provider.

SCIM 2.0 Compliance

This endpoint follows the SCIM 2.0 specification for resource type discovery.

Available Resource Types

• User - User resources at /Users endpoint

---

Important Notes!

• Use this endpoint to discover available resource types and their endpoints

• Each resource type maps to a specific schema

Authorizations

bearerAuth

AuthorizationstringRequired

API authentication using Bearer tokens. Include your API token in the Authorization header: Authorization: Bearer <your-api-token>

Tokens can be obtained from the Opsera platform's API token management interface.

Responses

200

Successfully retrieved resource types

application/scim+json

schemasstring[]OptionalExample: ["urn:ietf:params:scim:api:messages:2.0:ListResponse"]

totalResultsintegerOptionalExample: 1

get

/api/v2/scim/v2/ResourceTypes

HTTPcURLJavaScriptPython

GET /api/v2/scim/v2/ResourceTypes HTTP/1.1
Host: api.[organization].opsera.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

200

Successfully retrieved resource types

{
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:ListResponse"
  ],
  "totalResults": 1,
  "Resources": [
    {
      "id": "User",
      "name": "User",
      "endpoint": "/Users",
      "description": "User Account",
      "schema": "urn:ietf:params:scim:schemas:core:2.0:User",
      "schemaExtensions": [],
      "meta": {
        "resourceType": "ResourceType",
        "location": "/ResourceTypes/User"
      }
    }
  ]
}

Get a specific SCIM resource type

get

Returns a specific SCIM 2.0 resource type by its identifier.

SCIM 2.0 Compliance

This endpoint follows the SCIM 2.0 specification for resource type discovery.

Available Resource Type IDs

• User - User resource type

Authorizations

bearerAuth

AuthorizationstringRequired

API authentication using Bearer tokens. Include your API token in the Authorization header: Authorization: Bearer <your-api-token>

Tokens can be obtained from the Opsera platform's API token management interface.

Path parameters

idstringRequired

The resource type identifier

Example: User

Responses

200

Successfully retrieved resource type

application/scim+json

idstringOptionalExample: User

namestringOptionalExample: User

endpointstringOptionalExample: /Users

descriptionstringOptionalExample: User Account

schemastringOptionalExample: urn:ietf:params:scim:schemas:core:2.0:User

schemaExtensionsobject[]Optional

404

Resource type not found

application/scim+json

get

/api/v2/scim/v2/ResourceTypes/{id}

HTTPcURLJavaScriptPython

GET /api/v2/scim/v2/ResourceTypes/{id} HTTP/1.1
Host: api.[organization].opsera.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

{
  "id": "User",
  "name": "User",
  "endpoint": "/Users",
  "description": "User Account",
  "schema": "urn:ietf:params:scim:schemas:core:2.0:User",
  "schemaExtensions": [
    {}
  ],
  "meta": {
    "resourceType": "text",
    "location": "text"
  }
}