AccountInfoType

Whether to activate one-way SMS

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

Whether Voximplant notifications are required

Whether the account is ctive

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 state (US) or province (Canada), up to 100 characters. Examples: California, Illinois, British Columbia

The office ZIP

The payments limits applicable to each payment method

If salt string is specified, each HTTP request made by the Voximplant cloud toward the callback_url has 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 makes 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 has a JSON-encoded body that conforms to the AccountCallbacks 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, …)

Whether account is blocked by Voximplant admins

The notification language code (2 symbols, ISO639-1). Examples: en, ru

The account location (timezone). Examples: America/Los_Angeles, Etc/GMT-8, Etc/GMT+10

The min balance value to notify by email or SMS

Whether Voximplant news notifications are required

Whether to send an email when a JS error occures

Whether Bank card payments are allowed

Whether Bank invoices are allowed

Whether Robokassa payments are allowed

Whether Voximplant plan changing notifications are required

Whether the admin user permissions are granted