How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Sublime Security SCIM API

The SCIM API from Sublime Security — 8 operation(s) for scim.

Sublime Security SCIM API is one of 16 APIs that Sublime Security publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include SCIM. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 12 operations across 8 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, {scheme}://{server}.

12 operations 8 paths 26 schemas 1 DELETE8 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://platform.sublime.security
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Sublime Security SCIM API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 12

Across 8 paths, the API surfaces 12 operations — 1 DELETE, 8 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

SCIM 12
GET
/v0/scim/ResourceTypes
List SCIM resource types
listSCIMResourceTypes → 200
GET
/v0/scim/ResourceTypes/{id}
Get SCIM resource type
getSCIMResourceType 1 param → 200
GET
/v0/scim/Schemas
List SCIM schemas
listSCIMSchemas → 200
GET
/v0/scim/Schemas/{id}
Get SCIM schema
getSCIMSchema 1 param → 200
GET
/v0/scim/ServiceProviderConfig
Get SCIM service provider configuration
getSCIMServiceProviderConfig → 200
GET
/v0/scim/Users
List SCIM users
listSCIMUsers 3 params → 200
POST
/v0/scim/Users
Create SCIM user
createSCIMUser body → 201
DELETE
/v0/scim/Users/{id}
Delete SCIM user
deleteSCIMUser 1 param → 204
GET
/v0/scim/Users/{id}
Get SCIM user
getSCIMUser 1 param → 200
PATCH
/v0/scim/Users/{id}
Patch SCIM user
patchSCIMUser 1 param body → 200
PUT
/v0/scim/Users/{id}
Update SCIM user
updateSCIMUser 1 param body → 200
GET
/v0/scim/validate_auth
Validate SCIM specific auth
validateSCIMAuth → 200

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are Handler_typesSCIMSchemaAttribute (11 properties), UpdateSCIMUserInput (10 properties), Handler_typesSCIMUser (10 properties), CreateSCIMUserInput (10 properties). Each schema is shown below with its type and property counts.

Handler_typesSCIMPatchOperation
object
3 properties 1 required
Handler_typesSCIMServiceProviderConfigSort
object
1 property
Handler_typesSCIMMeta
object
Schema metadata
4 properties
Handler_typesSCIMSchemaSubAttribute
object
8 properties
CreateSCIMUserInput
object
10 properties 2 required
Handler_typesSCIMResourceType
object
8 properties
Handler_typesSCIMUserName
object
2 properties
Handler_typesSCIMServiceProviderConfigBulk
object
3 properties
Handler_typesListSCIMUsersResponse
object
5 properties
Handler_typesSCIMEmail
object
3 properties
Handler_typesSCIMSchemaExtension
object
2 properties
Handler_typesListSCIMResourceTypesResponse
object
5 properties
Handler_typesSCIMServiceProviderConfigFilter
object
2 properties
Handler_typesSCIMSchemaAttribute
object
11 properties
PatchSCIMUserInput
object
2 properties 2 required
Handler_typesListSCIMSchemasResponse
object
5 properties
Handler_typesSCIMSublimeUserExtension
object
1 property
Handler_typesSCIMServiceProviderConfigETag
object
1 property
Handler_typesSCIMServiceProviderConfigPatch
object
1 property
Handler_typesSCIMServiceProviderConfigChange
object
1 property
HandlersScimEchoResp
object
1 property
Handler_typesSCIMSchema
object
6 properties
Handler_typesSCIMUser
object
10 properties 2 required
Handler_typesSCIMAuthenticationScheme
object
4 properties
UpdateSCIMUserInput
object
10 properties 2 required
Handler_typesSCIMServiceProviderConfig
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sublime-security-scim-api-openapi.yml Raw ↑

Other APIs Sublime Security publishes across the network.

Sublime Security BinExplode API
Sublime Security Email Bombs API
Sublime Security Enrichment API
Sublime Security Events in the audit log API
Sublime Security Hunt Jobs API
Sublime Security Lists API
Sublime Security Live flow API
Sublime Security Mailboxes API
Sublime Security Message Groups API
Sublime Security Messages API
Sublime Security Organizations API
Sublime Security Roles API
Where this information came from

This is an independent, third-party profile of Sublime Security SCIM API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.