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/emburse-sap-person-controller-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: Hades Sap Person Controller API
version: v1
description: Sap Person Controller
servers:
- url: http://hades.pool
description: Generated server url
tags:
- name: sap-person-controller
description: Sap Person Controller
paths:
/v4/sap-persons:
post:
tags:
- sap-person-controller
summary: Create/update persons
description: This web service provides ability to create/update persons. TO BE USED ONLY BY SAP CONNECTORS.
operationId: sapPatchyPostBecauseReasons
parameters:
- name: chain-id
in: header
description: Reference used to track the flow of the request
required: true
schema:
type: string
- name: x-api-key
in: header
description: API key for Authentication
required: true
- name: customer-code
in: header
description: Unique customer identifier provided by Chrome River
required: true
responses:
'200':
description: All persons were processed successfully.
content:
'*/*':
schema:
type: array
items:
$ref: '#/components/schemas/Response'
'207':
description: Response consists of successes and failures.
content:
'*/*':
schema:
type: array
items:
$ref: '#/components/schemas/Response'
'400':
description: Processing or Data Issue - See errorMessage in response body for details
content:
'*/*':
schema:
type: array
items:
$ref: '#/components/schemas/Response'
'422':
description: All persons were not processed due to errors.
content:
'*/*':
schema:
type: array
items:
$ref: '#/components/schemas/Response'
'503':
description: Service unavailable.
content:
'*/*':
schema:
type: array
items:
$ref: '#/components/schemas/Response'
components:
schemas:
Response:
type: object
properties:
personUniqueId:
type: string
description: Unique identifier for a person
example: jdoe
result:
type: string
description: Result of operation
enum:
- SUCCESS
- FAIL
example: FAIL
errorMessage:
type: string
description: Error message provided for a FAIL result
example: firstName may not be empty