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.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/saleo-scim-20-provisioning-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

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