Reapit

Reapit Connect

Reapit's hosted OpenID Connect identity service, which fronts every other Foundations API. It supports the authorization code flow for user-context applications and the client credentials flow for server-to-server integrations, issuing bearer access tokens with a one-hour lifetime. Application scopes are selected at app registration in the developer portal and are granted per customer at install time. The OIDC discovery document is served anonymously at https://connect.reapit.cloud/.well-known/openid-configuration (HTTP 200) and shows an Auth0-backed tenant with PKCE (S256), device authorization, back-channel authentication, JWKS, dynamic client registration and token revocation endpoints.

Documentation GitHub

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/reapit-connect"

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 email required.

GitHub Google LinkedIn

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

API entry from apis.yml

aid: reapit:reapit-connect
name: Reapit Connect
description: Reapit's hosted OpenID Connect identity service, which fronts every other Foundations API.
  It supports the authorization code flow for user-context applications and the client credentials flow
  for server-to-server integrations, issuing bearer access tokens with a one-hour lifetime. Application
  scopes are selected at app registration in the developer portal and are granted per customer at install
  time. The OIDC discovery document is served anonymously at https://connect.reapit.cloud/.well-known/openid-configuration
  (HTTP 200) and shows an Auth0-backed tenant with PKCE (S256), device authorization, back-channel authentication,
  JWKS, dynamic client registration and token revocation endpoints.
humanURL: https://foundations-documentation.reapit.cloud/api/reapit-connect
baseURL: https://connect.reapit.cloud
tags:
- Authentication
- OpenID Connect
- Identity
tags_raw:
- Authentication
- OpenID Connect
- OAuth 2.0
- Identity
properties:
- type: Documentation
  url: https://foundations-documentation.reapit.cloud/api/reapit-connect
- type: OpenIDConnectDiscovery
  url: authentication/reapit-connect-openid-configuration.json
- type: WellKnown
  url: well-known/reapit-well-known.yml
- type: OAuthScopes
  url: scopes/reapit-scopes.yml
- type: Authentication
  url: https://connect.reapit.cloud/.well-known/openid-configuration
- type: SDK
  url: https://foundations-documentation.reapit.cloud/app-development/connect-session
- type: Troubleshooting
  url: https://foundations-documentation.reapit.cloud/troubleshooting/reapit-connect
- type: Changelog
  url: https://foundations-documentation.reapit.cloud/reapit-connect-updates