Saleo SCIM 2.0 Provisioning API

SCIM 2.0 (RFC 7643 / RFC 7644) user and group provisioning endpoint for the Saleo platform. Documented for customers through the Saleo Okta Integration Network application, which supports Create Users, Update User Attributes, Deactivate Users and Group Push (an Okta Group becomes a Saleo Team). Authentication uses a long-lived bearer API token minted from the Saleo Portal; tokens never expire but can be revoked. All SCIM resource endpoints — including ServiceProviderConfig, ResourceTypes and Schemas, which RFC 7644 allows to be served anonymously — return HTTP 401 with a conformant SCIM error envelope when unauthenticated, so the schema is not publicly readable and no OpenAPI is published.

API entry from apis.yml

apis.yml Raw ↑
name: Saleo SCIM 2.0 Provisioning API
description: SCIM 2.0 (RFC 7643 / RFC 7644) user and group provisioning endpoint for the Saleo platform.
  Documented for customers through the Saleo Okta Integration Network application, which supports Create
  Users, Update User Attributes, Deactivate Users and Group Push (an Okta Group becomes a Saleo Team).
  Authentication uses a long-lived bearer API token minted from the Saleo Portal; tokens never expire
  but can be revoked. All SCIM resource endpoints — including ServiceProviderConfig, ResourceTypes and
  Schemas, which RFC 7644 allows to be served anonymously — return HTTP 401 with a conformant SCIM error
  envelope when unauthenticated, so the schema is not publicly readable and no OpenAPI is published.
humanURL: https://help.saleo.io/articles/5029724323-how-to-configure-scim-within-saleo-s-okta-integration-network-app
baseURL: https://api.platform.saleo.io/scim/v2
tags:
- SCIM
- Identity Provisioning
- User Management
- Okta
properties:
- type: Authentication
  url: authentication/saleo-authentication.yml
- type: Conformance
  url: conformance/saleo-conformance.yml
- type: ErrorCatalog
  url: errors/saleo-problem-types.yml
- type: Conventions
  url: conventions/saleo-conventions.yml