| 908 | A parameter is not formatted correctly | Dynamic - describes the specific missing/invalid field | 400 | A required value is missing or in an invalid format for the specific field named in the description. |
| 1267 | B2B feature is not enabled or not configured properly | The B2B feature is not enabled or configured for your app. Please contact LoginRadius support for more information. | 403 | The tenant does not have the B2B Identity feature enabled, blocking access to any B2B route. |
| 1269 | Invalid provider in organization | The specified provider is not valid or not configured for this organization. Please check your configuration. | 400 | During a custom-IDP login: the provider identifier in the login callback doesn't have the expected format. |
| 1271 | Signup not allowed in organization | User signup is restricted for this organization. | 403 | A first-time login through an org connection with Just-In-Time provisioning enabled is rejected because neither the organization nor the app has a default member role configured to assign to the new user. |
| 2065 | Email domain not allowed in organization connection | The email domain used is not allowed for this organization connection. Please use an valid domain. | 403 | During Just-In-Time auto-provisioning on an org connection login, the authenticated user's email domain doesn't match the domain configured on that connection, or no email was returned by the identity provider at all. |
| 6002 | Access Unauthorized | Access Unauthorized, please use valid authorization to access this endpoint. | 403 | The caller's authentication/authorization does not permit access. |
| 6003 | Trial plan expired | The trial plan has expired. To continue using the service, please contact support. | 403 | The app's trial plan has expired. |
| 7900 | A parameter is not formatted correctly. | Dynamic - overridden per scenario | 400 | A field fails a specific format or structural validation rule. |
| 7914 | Post body is invalid | Please use a valid post body in JSON format. | 400 | A create request's body is missing, empty, or not valid JSON. |
| 7934 | Put body is invalid or empty | Please use a valid put body in JSON format in order to process this request. | 400 | An update request's body is missing, empty, or not valid JSON. |
| 8044 | Invalid Body | BodyType is selected as JSON, but the Body doesn't contain valid JSON data. Please input valid JSON data. | 400 | The request body is present but cannot be parsed into the expected structure. |
| 8045 | Email is missing | Cannot assign role to the user in the organization because the email is not available for the user. Please provide a valid uid. | 400 | The user has no primary or default email on file, which is required before an organization role can be assigned. |
| 8116 | Organization exists with the same name | Organization exists with the same name. Use a different organization name. | 409 | Another organization already uses the requested name, when creating or renaming an organization. |
| 8117 | Organization ID is invalid | This Organization ID is invalid, please use valid Organization ID. | 400 | A supplied organization id is in an invalid format. |
| 8118 | Organization not found | The entered organization or its configuration does not exist. | 404 | No organization exists for the given id. |
| 8119 | Invalid permission id | Invalid permission id, Please provide valid permission id. | 400 | A supplied permission id is in an invalid format, or does not correspond to an existing permission. |
| 8121 | Permission does not exist | Permission does not exist, Please provide valid permission id. | 404 | The additional-permission record targeted for removal does not exist for this user/organization combination. |
| 8122 | Permission id is required | Permission id is required, Please provide permission id. | 400 | A permission id was expected but not supplied. |
| 8123 | Duplicate role name | Duplicate role name, Please provide valid role name. | 409 | A role with the requested name already exists, when creating or renaming a role. |
| 8124 | Invalid role id | Invalid role id, Please provide valid role id. | 400 | Role id is not in the expected format. |
| 8125 | Role does not exist | Role does not exist, Please provide valid role id. | 404 | The role id does not correspond to an existing role. |
| 8126 | Role id is required | Role id is required, Please provide role id. | 400 | A role id was expected but not supplied. |
| 8127 | Role name is required | Role name is required, Please provide role name. | 400 | A role name was expected but not supplied. |
| 8128 | Default role cannot be deleted | Default role cannot be deleted, Please provide valid role id. | 403 | A delete request targets a role that is configured as the default/member role for the app or organization. |
| 8129 | Organization id is required | Organization id is required, Please provide organization id. | 400 | An organization id was expected but not supplied. |
| 8130 | User role already exists | User role already exists, Please provide valid role id. | 409 | The user is already assigned one or more of the roles being granted. |
| 8131 | User id is required | User id is required, Please provide user id. | 400 | A user id was expected but not supplied. |
| 8132 | User does not exist | User does not exist, Please provide valid user id. | 404 | The supplied user id does not correspond to an existing identity. |
| 8135 | User not found in organization | User not found in organization, Please provide valid user id. | 404 | The user has no role assignments within the specified organization. |
| 8137 | Invalid email | Invalid email, Please provide valid email. | 400 | The invitee's email address fails format validation. |
| 8142 | Role does not belong to organization | Role does not belong to organization, Please provide valid role id. | 403 | One or more roles assigned to a user in an organization are not valid tenant/org roles for that organization. |
| 8143 | Role does not belong to tenant | Role does not belong to tenant, Please provide valid role id. | 403 | A role referenced as tenant-level does not exist at the tenant level. |
| 8148 | Connection exists with the same name | Connection exists with the same name. Use a different Connection name. | 409 | Another connection on the organization already uses the requested name, when creating or renaming a connection. |
| 8149 | Domain exists with another connection | The domain is associated with a different connection. Please use a different organization domain. | 409 | The requested domain is already bound to a different connection on the organization. |
| 8150 | Domain does not exist within the organization | The provided domain is not associated with the organization. Please use a different organization domain. | 404 | A connection create/update references a domain that is not registered on the organization. |
| 8151 | Connection ID is invalid | This Connection ID is invalid, please use valid Connection ID. | 400 | A supplied connection id is in an invalid format, or does not match any connection on the organization. |
| 8152 | Connection config is invalid | Dynamic - names the missing required field(s) | 400 | The connection's type-specific configuration (e.g. SAML/OIDC settings) is missing one or more required fields, typically discovered when activating the connection. |
| 8154 | Domain ID is invalid | This Domain ID is invalid, please use valid Domain ID. | 400 | A supplied domain id is in an invalid format, or does not correspond to any domain record. |
| 8156 | Domain already verified | This Organization domain is already verified | 400 | A verification request targets a domain that is already marked verified. |
| 8157 | Domain exists with the same name | Domain exists with the same name. Use a different Domain name. | 409 | The domain name being added already exists in the organization. |
| 8159 | Organization member role is invalid | This Organization member role is invalid, please use valid Organization member role | 400 | An organization policy update sets a default member role that does not exist for the tenant or organization. |
| 8160 | Organization MFA enforcement not allowed | Organization MFA enforcement can not be enabled because MFA is disabled for the tenant. (message varies by scenario) | 403 | An organization policy update requests an MFA enforcement mode that conflicts with the tenant's MFA configuration: requiring something other than mandatory enforcement when the tenant mandates MFA; disabling enforcement while the tenant requires MFA; requesting mandatory enforcement with no MFA method enabled for the tenant; or requesting any non-"none" enforcement when the tenant has no MFA enabled at all. |
| 8161 | GroupRole exists with the same name | Connection GroupRole exists with the same name. Use a Connection GroupRole name. | 409 | Another group-role mapping on the connection already uses the requested name. |
| 8162 | GroupRole exists with the same GroupId | Connection GroupRole exists with the same GroupId. Use a different GroupRole GroupId. | 409 | Another group-role mapping on the connection already uses the requested external group identifier. |
| 8163 | GroupRole ID not exist | This GroupRole ID is not exist, Please use a valid GroupRole ID. | 404 | The group-role id supplied for an update does not correspond to an existing mapping on the connection. |
| 8164 | GroupRole ID is invalid | This GroupRole ID is invalid, Please use a valid GroupRole ID. | 400 | A supplied group-role id is in an invalid format. |
| 8166 | Status already updated | Status already updated, Please provide valid status. | 409 | The requested active/inactive status already matches the current status of the organization or connection being updated. |
| 8167 | Status update is invalid | Status update is invalid, Please provide valid status. | 400 | A status-update request did not include the required active/inactive flag. |
| 8168 | Failed to fetch Domain TXT record | Unable to fetch the Domain TXT record. Please ensure the domain is valid and correctly configured. | 400 | The DNS TXT record lookup performed while verifying a domain failed. |
| 8169 | Invitation not found | Invitation not found, Please provide valid invitation id. | 404 | No invitation record matches the given id. |
| 8170 | User already exist in an organization | User already exist in an organization, Please provide correct email id. | 409 | An identity already exists for the invited email and already holds role assignments in the target organization. |
| 8171 | invitation is active | Invitation is already active, Can not send the invite again. | 400 | An unexpired, unused invitation already exists for the same organization/email combination. |
| 8173 | Invitation token is not valid | Invitation token is not valid, this invitation either accepted, expired or revoked. | 400 | A social/OIDC/SAML login carrying a pending org-invitation token is rejected because the token doesn't resolve to a usable invitation, or (on first login) the authenticated identity's email doesn't match the invited email address. |
| 8174 | Inviter uid invalid or inviter does not exist/active | Inviter uid invalid or inviter does not exist/active, Please provide the valid inviter uid. | 400 | The inviter's identity cannot be resolved or is inactive. |
| 8175 | The invitation id/token is invalid | The invitation id is invalid. Please enter a valid invitation id. (message varies by scenario) | 400 | The invitation identifier is in an invalid format, or the invitation is in a state that makes it unusable. |
| 8176 | The Invitation URL is invalid | The Invitation is invalid, please whitelist the url. | 400 | The redirect URL supplied with the invitation is not on the app's allow-list. |
| 8177 | Organization domain is not verified | Organization domain is not verified, Please verify the domain. | 403 | A connection create/update references a domain that exists on the organization but has not completed verification. |
| 8178 | Organization domain can not be deleted | Organization domain can not be deleted, domain is currently being used in a connection. | 403 | A domain removal is rejected because the domain is currently referenced by an active connection. |
| 8180 | Organization is not active | This organization is currently inactive. Please activate it before performing any further actions. | 403 | The organization exists but has been deactivated. |
| 8181 | JIT policy not allowed in organization | Just-In-Time (JIT) provisioning is not allowed because there are no active connections configured for this organization. Please check your organization settings. | 403 | An update tries to enable Just-In-Time provisioning on an organization that has no active connections. |
| 8204 | Usage limit for this resource has been exceeded. | The usage limit for this resource has been exceeded. Please contact LoginRadius team for assistance. | 403 | The tenant or organization has reached its configured plan limit - for organizations, connections, domains, roles, or group roles - or an update supplies more domains than the organization's configured domain limit allows. |
| 8223 | Duplicate additional permission | This Additional permission already exists for this user in the org. Please provide a different additional permission. | 409 | The permission being granted is already assigned to this user within this organization. |
| 8225 | Maximum number of SCIM directory tokens reached | The organization SCIM directory already has the maximum number of tokens. Please delete an existing token before creating a new one. | 400 | The SCIM directory already holds the maximum number of active tokens allowed. |
| 8226 | At least one SCIM directory token is required | At least one SCIM directory token must remain active. The last token cannot be deleted. | 400 | Deleting the requested token would leave the SCIM directory with zero active tokens, which is not allowed. |
| 8227 | SCIM directory already configured for this organization | This organization already has an active SCIM directory configured. | 409 | The organization already has a SCIM directory, and a second one is being created (an org may have only one). |
| 8228 | SCIM directory not found for this organization | This organization already has an active SCIM directory configured. | 409 | No SCIM directory has been configured yet for the organization, and an operation (read, update, delete, or token management) requires one. |
| 8229 | SCIM directory token ID is required | A valid SCIM directory token ID must be provided to perform this operation. | 400 | A SCIM directory token id was expected but not supplied. |
| 8230 | Site is not configured for SCIM | Request couldn't be processed, SCIM feature is not enabled for this site. | 403 | The tenant does not have the SCIM feature enabled, blocking access to SCIM directory management routes. |
| 8231 | Name field is not allowed to update | Name field is not allowed to update. Please use the same name value in update request. | 400 | On a non-B2B-enabled app, an update attempts to change the name of an existing tenant-level role, which is immutable in that context. |
| 8232 | SCIM directory token not found | The requested SCIM directory token does not exist. | 404 | The token id supplied for deletion does not correspond to an existing token on the directory. |
| 8233 | Role name with reserved prefix cannot be deleted | Role names starting with lr: are reserved for internal roles and cannot be deleted. | 403 | A delete targets a role whose name uses the reserved internal prefix. |
| 8235 | Role name with reserved prefix cannot be updated | Role names starting with lr: are reserved for internal roles and cannot be updated. | 403 | An update targets a role whose name uses the reserved internal prefix. |
