The GetAccountInfo function result.
The allowed access entries (the API function names).
The custom data.
The account's email.
The first name.
The account's ID.
The last name.
The account's name.
Are the VoxImplant notifications required?
The account activation flag.
The account API key. Use password or api_key authentication to show the api_key.
The account's money.
The office address.
The billing address country code (2 symbols, ISO 3166-1 alpha-2). Examples: US, RU, GB
The company or businessman name.
The office phone number.
The office ZIP.
If salt string is specified, each HTTP request made by the Voximplant cloud toward the callback_url will have a salt field set to MD5 hash of account information and salt. That hash can be used be a developer to ensure that HTTP request is made by the Voximplant cloud
If URL is specified, Voximplant cloud will make HTTP POST requests to it when something happens. For a full list of reasons see the type field of the AccountCallback structure. The HTTP request will have a JSON-encoded body that conforms to the lAccountCallbacks structure
The UTC account created time in 24-h format: YYYY-MM-DD HH:mm:ss
The account's credit limit.
The currency code (USD, RUR, EUR, ...).
Is account blocked by VoxImplant admins or not.
The notification language code (2 symbols, ISO639-1). Examples: en, ru
The account location (timezone). Examples: America/Los_Angeles, GMT-08:00
The min balance value to notify by email or SMS.
Are the VoxImplant news notifications required?
The next charge date, format: YYYY-MM-DD
The tariff interval, format: YYYY-MM-DD 00:00:00
Is email sending on a JS error?
Is the bank card payments allowed?
Is the bank invoice allowed?
Is the robokassa payment system allowed?
Are the VoxImplant tariff changing notifications required?
The account's tariff ID.
The account's tariff name.
Set true to get the admin user permissions.