Is it easy or difficult to use our developer documentation? Let us know in this short survey ↗

On this page

SCIM Protocol

The System for Cross-domain Identity Management (SCIM) specification is a provisioning protocol to create, retrieve, update, and deactivate users and groups between Okta and downstream applications and directories.

For more background on the SCIM protocol, how it works, and particular use cases, see our topic on Understanding SCIM.

For a developer's guide to implementing the SCIM REST API with Okta and your application, the following links each contain all the information relevant to your specific SCIM:

Okta currently supports both Version 2.0 and Version 1.1 of the SCIM protocol specifications. If you haven't yet implemented SCIM, Okta recommends that you implement SCIM 2.0.

To work with Okta, your SCIM application must use RESTful endpoints constructed according to either the V2.0 (opens new window) or V1.1 (opens new window) SCIM protocol specification. The URL of your SCIM server is plugged into the SCIM integration in your Okta org. Okta then communicates with the endpoints through a series of HTTP requests and responses using POST, GET, PUT, and PATCH operations.

Differences between version 2.0 and 1.1

  • Different namespaces means that Version 2.0 URIs are not backwards compatible with 1.1:
    • V2.0:
      • urn:ietf:params:scim:schemas:core:2.0:User
      • urn:ietf:params:scim:schemas:extension:enterprise:2.0:User
    • V1.1:
      • urn:scim:schemas:core:1.0
      • urn:scim:schemas:extension:enterprise:1.0
  • The Service Provider configuration endpoint has no s at the end of the SCIM 2.0 endpoint:
    • V2.0:
      • /ServiceProviderConfig
    • V1.1:
      • /ServiceProviderConfigs
  • V2.0 also :