Authorizations
API key for authentication. Make sure to include the word apikey
, followed by a single space and then your token.
Example: apikey 1234$abcdef
Body
User's email address. This address will be used as client's email address by default.
User's password.
Client's company name.
User's type. It must be common
.
common
User's name. This name will be used as client's name by default.
User's phone number. This phone will be used as client's phone by default.
Client's seller ID.
Specify products if you want to override default product availability for this client.
null
– the product will inherit the default availability for this product.
true
– set personal availability for a client as available. Please be informed that product will not be enabled for a client until you
enable it and change the service status.
false
– set personal availability for a client as unavailable.
Language code.
de
, en
, ru
, zh
, az
Client's custom ID. You can use this field for your internal identification.
Client's country code.
System field:
true
— a test account;false
— a production account.
Response
OK.
User's ID.
User's email address.
User's name.
User's language.
Defines language of the control panel and email messages.
de
, en
, ru
, zh
, az
User's phone.
User's company.
Services provider ID.
User's account ID.
Deletion flag. If true
then user was deleted.
User's group in the current account.
IAM supports 5 groups:
- Users
- Administrators
- Engineers
- Purge and Prefetch only (API)
- Purge and Prefetch only (API+Web)
Email confirmation:
true
– user confirmed the email;false
– user did not confirm the email.
SSO authentication flag. If true
then user can login via SAML SSO.
Two-step verification:
true
– user enabled two-step verification;false
– user disabled two-step verification.
System field. List of auth types available for the account.
User's type.
common
, reseller
, seller
User activity flag.
List of user's clients. User can access to one or more clients.