Overview
Welcome to the ChainIT integration overview. ChainIT is used through its APIs: register applications in the Developer Portal, obtain clientId / clientSecret, and call the endpoints that match your product line. When your users need to sign in with a ChainIT account, use IDP or Hosted UI; for server-to-server automation with no interactive login, use M2M (client credentials).
Across flows, the same rules apply: credentials are issued once in the portal, tokens are short-lived, and secrets stay off public clients. What changes is whether a person signs in (no end user for M2M; a user for IDP/Hosted UI), which OAuth exchange you implement, and which portal fields matter—e.g. PKCE for public IDP clients, server-only clientSecret for M2M and Hosted UI server calls, and no UserInfo for M2M tokens.
Application walkthroughs
M2M
Your backend exchanges client credentials for an access token and calls ChainIT APIs—no user login or browser secrets.
IDP (Login with ChainIT)
OIDC authorization with PKCE: user signs in with ChainIT, returns with a code, and your backend exchanges it for tokens—same pattern as Login with Google.
Hosted UI
SDK-hosted OTP, agreements, and verification in your brand; tokens delivered on success while the clientSecret stays on your server.
Use Application types for comparison tables and field guidance. The M2M, IDP, and Hosted Auth guides are the canonical references—there is no separate “framework-only” track that replaces them.
Quickstart
Pick Hosted UI, IDP, or M2M. Create the matching application type in the Developer Portal first, then open the guide below.
Hosted UI
Managed, branded sign-up and verification—SDK-driven UI, no custom auth screens.
Open guideIDP
Same idea as “Login with Google”: a “Login with ChainIT” button using OAuth/OIDC and PKCE—your app owns the shell around redirects.
Open guideM2M
Server-side client credentials: exchange for a bearer token, then call ChainIT APIs from your backend.
Open guideQuick links
Need a sandbox Admin login first? — Request a sandbox
Sign in and use the Developer Portal — Getting Started
Connect your AI coding agent — MCP server
Compare M2M, IDP, and Hosted UI — Application types
Implement backend client credentials — M2M
Implement “Login with ChainIT” (OAuth/OIDC + PKCE) — IDP
Use managed onboarding / verification UI — Hosted UI
Validate tokens — Token validation
Harden my integration — Security best practices
Monitor apps with alerts — Alerting overview
Suggested reading order
- Getting Started — portal sign-in (required before creating apps).
- Application types — pick M2M vs IDP vs Hosted UI.
- The guide for your choice — follow it end-to-end, including security sections.