LoginRadius API

Name: LoginRadius API API
Brand: LoginRadius API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey18 EndpointsREST

For Agents

Register users, authenticate with email and password, manage profiles and access tokens, and administer roles and accounts in LoginRadius CIAM.

Quickstart

Get started with LoginRadius API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"register a new user"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with LoginRadius API API.

Authenticate users via POST /identity/v2/auth/login and issue an access token

Validate or invalidate an access token through /identity/v2/auth/access_token endpoints

Initiate forgot-password and reset-password flows on /identity/v2/auth/password

GET STARTED

Start building with LoginRadius API API

Explore with Jentic

View OpenAPI Document

Use for: Register a new user with email and password, Authenticate a user and return an access token, Validate the access token attached to this request, Reset the password for a user who forgot theirs

Not supported: Does not handle SSO federation configuration, MFA enrolment beyond basic flows, or organisation/tenant directory structures — use for end-user authentication, profile management, and role administration only.

Jentic publishes the only available OpenAPI document for LoginRadius API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for LoginRadius API, keeping it validated and agent-ready. LoginRadius is a customer identity and access management (CIAM) platform that exposes registration, login, password recovery, profile management, email verification, role management, and account administration operations. The spec covers 18 endpoints across the auth and manage namespaces, supporting both end-user flows (register, login, change password) and back-office tasks (look up account by uid, manage roles).

Use Cases

Patterns agents use LoginRadius API API for, with concrete tasks.

★ Email and Password Registration Flow

Register new users from a sign-up form via POST /identity/v2/auth/register and trigger an email verification with the spec's email-verify flow. The same payload accepts custom profile fields so onboarding metadata is captured at sign-up.

POST /identity/v2/auth/register with email='jane@example.com', password='S3cure!', and FirstName='Jane' to create the account.

Token-based Login for SPAs

Authenticate single-page applications by calling POST /identity/v2/auth/login and storing the returned access token client-side. Each subsequent request validates the token via GET /identity/v2/auth/access_token/validate so backends can trust the bearer.

POST /identity/v2/auth/login with email and password, then call GET /identity/v2/auth/access_token/validate with the returned token.

Self-service Password Reset

Allow users to recover access by initiating POST /identity/v2/auth/password/forgot, which emails a reset link, then completing PUT /identity/v2/auth/password/reset with the token and new password. This avoids manual support tickets for forgotten credentials.

POST /identity/v2/auth/password/forgot with email='jane@example.com' to send the reset email.

Role-based Access Control Setup

Provision roles for a new application by calling POST /identity/v2/manage/role and listing them with GET /identity/v2/manage/role. Roles can later be attached to users via the manage account endpoints to enforce scoped access.

POST /identity/v2/manage/role with body Name='editor' to create the role.

AI Agent User Provisioning via Jentic

An agent that handles HR onboarding can register new employee accounts in LoginRadius and assign them a starter role through Jentic. The API key stays in the vault so the agent never sees the secret.

Through Jentic, search 'register a new user', load the LoginRadius POST /identity/v2/auth/register operation, and execute it with the new hire's email.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for loginradius api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/identity/v2/auth/register

POST

/identity/v2/auth/login

Authenticate with email and password

GET

/identity/v2/auth/access_token/validate

Validate an access token

POST

/identity/v2/auth/password/forgot

Trigger forgot-password email

PUT

/identity/v2/auth/password/reset

Reset password with token

GET

/identity/v2/manage/account/{uid}

Look up an account by uid

POST

/identity/v2/manage/role

Create a new role

POST

/identity/v2/auth/register

POST

/identity/v2/auth/login

Authenticate with email and password

GET

/identity/v2/auth/access_token/validate

Validate an access token

POST

/identity/v2/auth/password/forgot

Trigger forgot-password email

PUT

/identity/v2/auth/password/reset

Reset password with token

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

LoginRadius apikey and apisecret are stored encrypted in the Jentic vault and injected at execution time, so the raw values never reach the agent's prompt or logs.

Intent-based discovery

Agents search by intent (e.g. 'register a user' or 'reset a password') and Jentic returns the matching LoginRadius operation with its input schema.

Time to first call

Direct LoginRadius integration: 1-2 days to wire up registration, login, token validation, and reset flows. Through Jentic: under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auth0 Management API

Mature CIAM platform with extensive enterprise SSO and rules support

Choose Auth0 when you need enterprise SSO, custom rules, and a large ecosystem of pre-built integrations.

Alternative

Okta API

Identity platform focused on workforce and customer identity at enterprise scale

Use Okta when the buyer already has an Okta workforce contract or needs deep directory and policy features.

Alternative

Stytch API

Modern passwordless and biometric-first authentication API

Choose Stytch when passwordless flows (magic link, OTP, WebAuthn) are the primary authentication pattern.

Alternative

Clerk Backend API

Developer-friendly auth with prebuilt React components and session management

Pick Clerk when the front-end is React/Next.js and you want drop-in UI components alongside the API.

FAQs

Specific to using LoginRadius API API through Jentic.

Why is there no official OpenAPI spec for LoginRadius API?

LoginRadius does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LoginRadius API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the LoginRadius API use?

LoginRadius uses an API key passed as a query parameter (apikey). Manage endpoints additionally require an apisecret. Through Jentic both values are stored encrypted in the vault and injected at execution, never reaching the agent's context.

Can I implement self-service password reset with the LoginRadius API?

Yes. Call POST /identity/v2/auth/password/forgot to email the user a reset link, then complete the flow with PUT /identity/v2/auth/password/reset using the token from the email.

How do I register a new user through Jentic?

Run `pip install jentic`, search Jentic for 'register a new user', load the LoginRadius POST /identity/v2/auth/register operation, and execute it with the user's email and password. Jentic returns the new uid.

What are the rate limits for the LoginRadius API?

Rate limits depend on your LoginRadius plan tier. The spec does not embed specific numbers. Implement exponential backoff on HTTP 429 responses to stay within quota.

Can I manage user roles via the LoginRadius API?

Yes. Use POST /identity/v2/manage/role to create roles, GET /identity/v2/manage/role to list them, and DELETE /identity/v2/manage/role/{roleName} to remove a role.