Skip to main content

Overview

LoginRadius Account APIs provide powerful administrative capabilities for managing customer profiles within the Cloud Directory. These APIs are designed to be used by system administrators or securely through backend systems. With functions that override default workflows, the Account APIs allow for comprehensive control over registration, profile data access, account updates, and deletion.

⚠️ Account APIs have higher privileges and can override some security settings in the Admin Console. Use them with caution to ensure security.

API Security

All Account APIs require the LoginRadius API Secret, which provides management-level access and should never be exposed in client-side applications.

How to Retrieve Your API Secret:

  1. Log in to your LoginRadius Admin Console.
  2. Navigate to Tenant Settings > General > API Configuration.
  3. Copy the API Secret securely for use in backend requests.

Key Features and Use Cases

  • Custom Account Creation: Register users directly without standard email verification flows.
  • Centralized Profile Access: Retrieve user details using identifiers like UID, email, username, or phone number.
  • Administrative Updates: Modify user information, set passwords, or update security questions.
  • Account Removal: Delete customer accounts or specific identifiers for identity cleanup.

These APIs are commonly used for:

  • Backend user provisioning and onboarding
  • Data sync between systems
  • Admin-driven support and recovery processes
  • Privacy-driven deletion workflows

Common Account API Endpoints

These endpoints allow administrators to register new users in the Cloud Directory and verify their accounts. They bypass standard email verification flows, enabling direct user provisioning.

EndpointDescription
Account CreateRegister a user using the required fields.
Email Verification TokenGenerate a token to verify the user email manually.
Forgot Password TokenGet a token to trigger a password reset email.

Best Practices

  • Use Account APIs only in secure backend environments to avoid exposing the API Secret.
  • Log and audit all account-related actions, especially deletions and impersonation.
  • Store the API Secret securely using environment variables or secret managers.
  • Apply role-based access to restrict who can invoke these APIs.