Skip to main content

Developer Portal — Getting Started

The Developer Portal is where you register ChainIT applications and obtain clientId and clientSecret. You must sign in first; only then can you create applications or rotate credentials. This page walks through portal login (QR-based), prerequisites, creating your first application in the console, and copying credentials safely. For the field-by-field walkthrough, see Create application — step-by-step.

Sign in to the Developer Portal​

How to sign in to the Developer Portal

A quick demo to get you up and running.

This walkthrough shows QR-based access to the Developer Portal: opening the sign-in page, scanning the code with the ChainIT mobile app, and approving the session so your browser lands in an authenticated console. Use it alongside the written steps below for roles, prerequisites, and creating your first application.

Create your first applicationCreate application — step-by-stepExplore documentation

How Developer Portal login works​

The portal does not use a traditional password field for day-to-day access. Instead it pairs something you display in the browser (a QR code bound to a short-lived login session) with something you prove on your phone (the ChainIT mobile app, already tied to your verified user account). That split is intentional: your laptop browser never handles a long-lived portal password, and phishing against a static password field is avoided.

Typical flow

  1. Open the Developer Portal sign-in page: ChainIT Developer Portal (QR sign-in).
  2. The page renders a QR code tied to a pending login. Leave the tab open until you complete the steps on your phone.
  3. On your phone, open the ChainIT app, choose Scan QR, and scan the code from the browser.

Scan the QR code to Login to ChainIT

Open the ChainIT mobile app on your phone, scan the QR code, and confirm the login on your phone.

Waiting for authentication...
Expires in: 4:59
Download on the App StoreGet it on Google Play
Illustration — representative UI; QR pattern is not scannable.

ChainIT mobile app (account and download)​

You need the ChainIT ID mobile application to complete QR login. Install it from the App Store or Google Play, register using your organization’s process, and complete any required verification. If you cannot access the app, you cannot open the Developer Portal through this path—contact your organization administrator.

StoreDownload
App Store (iOS)ChainIT ID on the App Store
Google Play (Android)ChainIT ID on Google Play
Quick links (after you are signed in)

Prerequisites: who can create applications​

Your user must carry one of the following roles in ChainIT:

Role categoryRole codeDescription
DeveloperdeveloperStandard access to register and manage integrations for your org.
Organization adminorganization_adminBroader org administration; can manage apps and members depending on policy.

If you can log in but do not see Create application, your account likely lacks the role—ask an organization admin to grant developer access.

Register your first application​

After a successful portal login:

  1. Open the Applications section of the console.
  2. Choose Create / Register application.
  3. Select an application type (M2M, IDP, or Hosted UI). If you are unsure, stop and read Application types—the fields you see depend entirely on this choice.
  4. Fill in the required fields for that type (for example redirect URIs and origins for IDP, scopes for M2M, branding for Hosted UI).
  5. Save the application. You can edit many settings later, but you should still choose the correct type up front because it selects the OAuth topology your code must implement.
Field cheat sheet

For a tabular view of which portal properties each type supports, use the matrix on Application types.

Retrieve and store credentials​

When registration completes, the portal shows clientId and clientSecret—often only once for the secret.

{
  "client_id": "chainit_abc123xyz789",
  "client_secret": "sk_live_secure_secret_key"
}

Copy them into a password manager or secret store (for example cloud secret manager, CI sealed secrets, or .env files that are never committed). Rotate promptly if a secret is exposed.

Never expose clientSecret

Do not embed clientSecret in SPAs, mobile binaries, or public repositories. Hosted UI and M2M always use the secret on a server; IDP public clients use PKCE instead of shipping a secret to the browser.

Next steps​

Next steps