Automatic Call Distribution for Salesforce

Create Task

Service Parameters for the create task service are -

•PBX Id

•Org Id

•Activity Look Up Id

•Caller Id / IVR Id

•PBX Token

•Due Date

•Notes (Optional)

To create a task in the Salesforce the Task post call has to be used from the PBX:

Body:

{

"ActivityLookupId": "2E816A-2ED7BF-7EDDA4",

"CallerId": "000497852416200xxx",

"IVRId": "",

"DueDate": "2021-03-22",

"Notes": "These are my Notes",

"Token": "<provide here or with Bearer Token in Header>"

}

Parameters:

The first parameter in the path <PBXId><OrgId> is the PBX Id joined with the Org Id (without a blank or separator).

The Activity Look up Id is unique id of the activity look up

The parameters callerid and ivrid are optional, but at least one has to be used.

Due date requires a date format string

Notes field is optional but can be used to add comment to the task.

To call Task service a PBX-Token has to be used. The PBX-Token can be requested inside ACDPortal and has to match the PBX it has been issued for.

The Token has to be delivered in the call either as a post-Param or in the HTTP Header as Bearer Authorization:

Authorization: Bearer <theToken>

Create Task Example:

https://acd1.miragecloud.com/acd/api/Task/E0DE26-56A3C0-65B26700D24000000HxH6DSF

{

"ActivityLookupId": "8A3B46-CF21DB-650C45",

"CallerId": "+497525431242",

"IVRId": "",

"DueDate": "16.04.2021",

"Notes": "These are my test Notes",

"Token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJBQ0RQdCIsImF1ZCI6IkUwQkUyNi01OEEzQzAtNjVCMjY3In0"

}