Reclaim.ai Scim API
The Scim API from Reclaim.ai — 6 operation(s) for scim.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/reclaim-ai-scim-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.
OpenAPI Specification
openapi: 3.2.0
info:
title: Reclaim account-time-schemes SCIM API
description: Reclaim's awesome API
contact:
name: Reclaim.ai Inc.
url: http://reclaim.ai
email: info@reclaim.ai
license:
name: Reclaim 9.9
url: http://reclaim.ai
version: '0.1'
servers:
- url: https://api.app.reclaim.ai
description: Base URL declared by the provider in apis.yml (roadmap#122).
tags:
- name: Scim
paths:
/scim/v2/Groups:
get:
operationId: getGroups
responses:
'200':
description: getGroups 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
/scim/v2/ResourceTypes:
get:
operationId: getResourceTypes
responses:
'200':
description: getResourceTypes 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
/scim/v2/Schemas:
get:
operationId: getSchemas
responses:
'200':
description: getSchemas 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
/scim/v2/ServiceProvider:
get:
operationId: getServiceProvider
responses:
'200':
description: getServiceProvider 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
/scim/v2/Users:
get:
operationId: getUsers
parameters:
- name: attributes
in: query
schema:
type:
- array
- 'null'
items:
type: string
- name: startIndex
in: query
schema:
type:
- integer
- 'null'
format: int32
- name: count
in: query
schema:
type:
- integer
- 'null'
format: int32
- name: filter
in: query
schema:
type:
- string
- 'null'
responses:
'200':
description: getUsers 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
put:
operationId: putUser
requestBody:
content:
application/scim+json:
schema:
$ref: '#/components/schemas/ScimUser'
application/json:
schema:
$ref: '#/components/schemas/ScimUser'
required: true
responses:
'200':
description: putUser 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
post:
operationId: createUser
requestBody:
content:
application/scim+json:
schema:
$ref: '#/components/schemas/ScimUser'
application/json:
schema:
$ref: '#/components/schemas/ScimUser'
required: true
responses:
'200':
description: createUser 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
/scim/v2/Users/{id}:
get:
operationId: getUser
parameters:
- name: id
in: path
required: true
schema:
type: string
responses:
'200':
description: getUser 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
put:
summary: Using Map here instead of @Body ScimUser because we suspect that there are arbitrary properties that are being sent from the SCIM providers that would be useful for us to capture so that we can provide richer analytics facets.
description: Using Map here instead of @Body ScimUser because we suspect that there are arbitrary properties that are being sent from the SCIM providers that would be useful for us to capture so that we can provide richer analytics facets.
operationId: putUserId
parameters:
- name: id
in: path
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
type: object
additionalProperties: true
application/scim+json:
schema:
type: object
additionalProperties: true
required: true
responses:
'200':
description: putUserId 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
delete:
operationId: deleteUser
parameters:
- name: id
in: path
required: true
schema:
type: string
responses:
'200':
description: deleteUser 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
patch:
operationId: patchUser
parameters:
- name: id
in: path
required: true
schema:
type: string
requestBody:
content:
application/scim+json:
schema:
$ref: '#/components/schemas/ScimPatch'
application/json:
schema:
$ref: '#/components/schemas/ScimPatch'
required: true
responses:
'200':
description: patchUser 200 response
content:
application/scim+json:
schema:
type: object
security:
- Authorization:
- ROLE_API
tags:
- Scim
components:
schemas:
ScimEmail:
type: object
properties:
type:
type: string
value:
type: string
display:
type: string
primary:
type: boolean
ScimName:
required:
- familyName
- givenName
type: object
properties:
givenName:
type: string
familyName:
type: string
ScimUser:
type: object
properties:
userName:
type: string
name:
$ref: '#/components/schemas/ScimName'
id:
type: string
emails:
type: array
items:
$ref: '#/components/schemas/ScimEmail'
active:
type: boolean
displayName:
type: string
title:
type: string
userType:
type: string
externalId:
type: string
meta:
$ref: '#/components/schemas/ScimMeta'
schemas:
type: array
items:
type: string
scimEnterprise:
$ref: '#/components/schemas/ScimEnterprise'
reclaimExtension:
$ref: '#/components/schemas/ScimReclaimExtension'
attributes:
type: object
additionalProperties: true
ScimPatch:
required:
- Operations
- schemas
type: object
properties:
schemas:
type: array
items:
type: string
Operations:
type: array
items:
$ref: '#/components/schemas/ScimOperations'
ScimOperations:
required:
- op
- path
- value
type: object
properties:
op:
type: string
path:
type: string
value:
description: This getter handles the type switching
valueAsMap:
type: object
additionalProperties: true
description: This getter handles the type switching
ScimReclaimExtension:
type: object
properties:
location:
type:
- string
- 'null'
hireDate:
type:
- string
- 'null'
jobCategory:
type:
- string
- 'null'
orgRole:
type:
- string
- 'null'
team:
type:
- string
- 'null'
description: Encapsulates the reclaim-defined core attributes extending the SCIM user resource.
ScimEnterprise:
type: object
properties:
employeeNumber:
type:
- string
- 'null'
costCenter:
type:
- string
- 'null'
organization:
type:
- string
- 'null'
division:
type:
- string
- 'null'
department:
type:
- string
- 'null'
manager:
allOf:
- $ref: '#/components/schemas/ScimManager'
ScimMeta:
type: object
properties:
resourceType:
type: string
created:
type: string
format: date-time
ScimManager:
type: object
properties:
displayName:
type:
- string
- 'null'
value:
type:
- string
- 'null'
ref:
type:
- string
- 'null'
securitySchemes:
Authorization:
type: oauth2