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.

GitHub

Documentation

📖
Documentation
https://foundations-documentation.reapit.cloud/api/reapit-connect
📖
Authentication
https://connect.reapit.cloud/.well-known/openid-configuration
📖
Troubleshooting
https://foundations-documentation.reapit.cloud/troubleshooting/reapit-connect

SDKs

📦
SDK
https://foundations-documentation.reapit.cloud/app-development/connect-session

Other Resources

🔗
OpenIDConnectDiscovery
https://raw.githubusercontent.com/api-evangelist/reapit/refs/heads/main/authentication/reapit-connect-openid-configuration.json
🔗
WellKnown
https://raw.githubusercontent.com/api-evangelist/reapit/refs/heads/main/well-known/reapit-well-known.yml
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/reapit/refs/heads/main/scopes/reapit-scopes.yml
🔗
Changelog
https://foundations-documentation.reapit.cloud/reapit-connect-updates

API entry from apis.yml

apis.yml Raw ↑ 
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
- 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