LoginRadius API Documentation

This is the complete API documentation for connecting to the LoginRadius API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet LoginRadius: Manage customer identities, authentication, and access security. Keep reading to get started.

Quickstart

Before you run your first LoginRadius request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one LoginRadius connection — create or choose one in Connections. Note its connectionId.

Every LoginRadius action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/loginRadius/latest/actions/{actionSlug}

You need a MindCloud API Key and a LoginRadius connection. Then call an action such as Check Email Availability:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/loginRadius/latest/actions/check-email-availability" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected LoginRadius account that should run the action. MindCloud stores and refreshes the LoginRadius credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

LoginRadius actions

All 40 published actions for this LoginRadius version. Each page documents the endpoint, arguments, and response controls.

• POSTAdd Email
• PUTAssign Roles in Organization
• PUTChange Phone Number
• GETCheck Email Availability
• POSTCreate Account
• POSTCreate Custom Object
• POSTCreate Organization
• POSTCreate Organization Connection
• POSTCreate Role
• POSTCreate Webhook Configuration
• DELETEDelete Account by Email
• DELETEDelete Account by UID
• DELETEDelete Custom Object by ID
• PUTForgot Password
• GETGenerate Backup Codes
• GETGet Server Time
• DELETEInvalidate Access Token
• GETList Organization Connections
• GETList Organizations
• GETList Roles
• GETList User Profiles
• GETList Webhook Configurations
• POSTLogin With Credentials
• GETMFA Login
• GETQuery Custom Objects
• PUTResend Verification Email
• PUTReset Backup Codes
• GETRetrieve Access Token Information
• GETRetrieve Account
• GETRetrieve Account by UID
• GETRetrieve Active Session
• GETRetrieve Custom Objects
• GETRetrieve MFA Settings
• GETRetrieve Organization Details
• GETRetrieve Role by ID
• GETRetrieve Roles by UID
• GETRetrieve User
• DELETESend User Deletion Email
• PUTUpdate Password
• PUTVerify Email

Related apps

More IT Operations apps on the Universal API, behind the same REST shape. Or browse all apps.

GitHubNetlifyMySQLPostgreSQLFirebasePagerDutyGoogle Workspace AdminAdalo