continue from part II…

action=addcallback

The callback time is specified in MILLIS, which is the epoch time in a computer system. For example, if you use Java, you can get the current time in epoch time using System.getCurrentTimeMillis();

You can also specify the callback time in NEXTSECONDS, which is time in the next x seconds.

Use ID= callback ID if you are updating an existing record.

Use AGENT= agent login name to specify which agent should perform the callback.

The customer related information are specified in CUSID, PHONE, EXT.

Callback note is specified in NOTE.

If call back is finished, use DONE=1.

continue from part I…

crmentid is the entity ID of the entity table (Customer, Organization, Potential). By default it is the Customer table. Use MOD=ORG or MOD=POT for other tables.

To specify who performed the action, use AGENT= agent ID.

action=set

Specify name= column name, and value= the desired value.

If you want to set and get category by name, use CUSTOMER_CATNAME for the column name.

To set and get agent field by name, replace the _ID in the column name with _NAME.

action=get

Same as above, except you do not need to specify value parameter.

action=addnote

To add note to an entity, specify note= for the notes. To specify which entity, use the above MOD parameter.

First, figure out the URL and required post parameters from Setup > Website > API page. The document related to “cusact” is documented on that page. However, there are other actions you can use.

action=add

This is used to add an entity to the CRM. By default, the entity is a Customer entity. But you can specify MOD=POT, or MOD=ORG, for potential or organization entity.

Normally, Voicent CRM will try to merge the new record with existing entities. However, if you specify MERGE=skip, then the new record will be created always.

if MERGE=no, then no update to the existing record will happen.
if MERGE=yes, then the new values will replace the old one.

By default, the new values will only be updated if the existing value is empty.

The merge operation is performed by checking emails and phone numbers. Since this is an expensive operation, you should specify the search order. MERGEBYEMAIL=1 will cause the system to check the email address first, then the phone numbers.

The rest of the parameter names are the column names of the entity table.