Alphaus Iam API
(BETA) IAM API. Base URL: https://api.alphaus.cloud/m/blue
Operations 39
GET
/iam/v1/experimentalui/preferences
Gets experimental UI preferences for the authenticated MSP.
#
PUT
/iam/v1/experimentalui/preferences/{componentId}
Creates or updates an experimental UI preference for a specific component.
#
GET
/iam/v1/grouprootusers
WORK-IN-PROGRESS: Retrieves all the existing group root users asscoiated with the organization.
#
POST
/iam/v1/grouprootusers
WORK-IN-PROGRESS: Creates a new root user for a billing group or access group.
#
GET
/iam/v1/grouprootusers/{id}/features
WORK-IN-PROGRESS: Retrieves the features available to a user on an Alphaus product.
#
PUT
/iam/v1/grouprootusers/{id}/features
WORK-IN-PROGRESS: Updates the features available to a user on an Alphaus product.
#
GET
/iam/v1/ipfilters
Lists all IP filters. At the moment, this API is only available to root users.
#
POST
/iam/v1/ipfilters
Creates an IP filter item for IP blacklisting or whitelisting. At the moment, this API is only available to root users.
#
DELETE
/iam/v1/ipfilters/{id}
Deletes an IP filter item. At the moment, this API is only available to root users.
#
GET
/iam/v1/metadata/{id}
WORK-IN-PROGRESS: Get Sub User Metadata for login user's organization based on user identity
#
GET
/iam/v1/mfausers
WORK-IN-PROGRESS: List MFA users info for login user's organization based on status.
#
POST
/iam/v1/partners/{id}/token
BETA: Creates a partner token for custom integrations. Available only to Ripple and Cover users.
#
POST
/iam/v1/partners/{id}/token:refresh
BETA: Refreshes an expired partner token. Only partners are expected to call this API.
#
POST
/iam/v1/password:reset
WORK-IN-PROGRESS: Validate reset password link and proceed to update password
#
GET
/iam/v1/permissions
WORK-IN-PROGRESS: Lists all permissions based on the input's scope. For reference, supported permissions can be found on [https://github.com/mobingi/rbac-permissions].
#
POST
/iam/v1/roles
WORK-IN-PROGRESS: Creates a role. If your `permissions` list contains an `Admin` entry, all other entries will be discarded except `Admin`. Roles are root user-level. That means al
#
DELETE
/iam/v1/roles/{namespace}/{name}
WORK-IN-PROGRESS: Deletes a role. Deleting a role will also remove all mappings.
#
PUT
/iam/v1/roles/{namespace}/{name}
WORK-IN-PROGRESS: Updates a role. If role name is different, rename mapped role name.
#
POST
/iam/v1/userroles
WORK-IN-PROGRESS: Maps roles to a subuser. You can only map (or attach) up to 5 roles to a user per namespace. There is no limit for filtering rules per user.
#
PUT
/iam/v1/userroles
WORK-IN-PROGRESS: Updates user-to-role mappings. You can only map (or attach) up to 5 roles to a user per namespace. There is no limit for filtering rules per user.
#
GET
/iam/v1/users/{id}
Gets subuser information. This call includes all of the subuser metadata. See [https://alphauslabs.github.io/blueapi/] for the list of supported attributes. If the `{name}` paramet
#
GET
/iam/v1/whoami
Gets user information about the caller. This call includes all of the user metadata. See [https://alphauslabs.github.io/blueapi/] for the list of supported attributes.
#