API DOCUMENTATION Last Update: July 2025

Update User Information

Update an account user 's information.

 

Headers

  Key   Value   Note
api_access_key user_api_key Optional

 

 

The data to be submitted to the API is composed of the following fields:

 

  field   Example   Note
user_id john1970 Required
user_password 1959caadac9b13dcb3 Required if not included in the headers
type user_update Required
account_id greatwidgets Required
user_name janeclerk Required
user_new_password pa$$wo0rd Optional
user_first_name Jane Optional
user_last_name Doe Optional
user_custom1 Melbourne Office Optional
user_PIN 1234 Optional
language_selector EN Optional
language_custom Yes or No Optional
timezone_selector 68 Optional
user_role K Optional
allowed_campaigns all or campaign id(s) or none Optional
Output Format:
output JSON or XML Optional. If not provided, defaults to XML
callback someFunctionName Optional: JSONP format
condensed yes Optional (No white space)
Applies only to JSON(P) output

 

Notes:

  • Headers: the user_api_key value can be included in either the header section or the body of the request. If the key is provided in both locations, the API will process and validate only the value provided in the headers.

  • The user_name cannot be changed, but must be provided to know which user is being updated.
  • The user_PIN is an API-specific field made available for custom applications such as a physical terminal. It cannot be defined or edited in the web interface. It MUST be unique to each user in an account.
  • You can find a list of language two-letter codes in the Available Languages reference page
  • You can find a list of timezone codes in the Timezones reference page
  • The allowed_campaigns consists of: (see examples below)
    • A single entry "all"
    • A single entry "none"
    • Multiple entries of campaign ID (see example below)
    • Administrator (A) users are not affected by this parameter and are always set to access all campaigns.
  • The user_role is based on the roles listed in the User Permission Levels reference page.
  • The language_custom is used only for custom applications that need a flag to indicate if the user has a custom language definition store locally (elsewhere) or not.

 

Example PHP Request:

If you are using PHP, the $data array would look like this:

  1. $data['user_id'] = 'john1970';
  2. $data['user_password'] = '1959caadac9b13dcb3';
  3. $data['type'] = 'process_user';
  4. $data['account_id'] = 'greatwidgets';
  5. $data['user_action'] = 'new';
  6. $data['user_name'] = 'janeclerk';
  7. $data['user_password1'] = 'pa$$w0rd';
  8. $data['user_password2'] = 'pa$$w0rd';
  9. $data['user_first_name'] = 'Jane';
  10. $data['user_last_name'] = 'Doe';
  11. $data['user_custom1'] = 'Melbourne Office';
  12. $data['language_selector'] = 'EN';
  13. $data['timezone_selector'] = '68';
  14. $data['user_role'] = 'K';
  15. $data['allowed_campaigns'] = '12971184024723,0239471023412';
  16. or
  17. $data['allowed_campaigns'] = 'all';
  18. or
  19. $data['allowed_campaigns'] = 'none';

 

Success XML Response (New / Updated User):

  1. <response status="success">
  2. </response>

 

Error XML Response:

  1. <response status="error">
  2. <error>Error message</error>
  3. </response>