Contact Activities (Events)

API Set Name: contactactivities

• POST /contactactivities
• GET /contactactivities

API Description and Functional Purpose:

The contact activities collection contains all contact-related activities such as opens, clicks, sends and any other user-defined actions. Contact activities are also referred to as "events".

Additional information:

• Contact activities are associated to the contact via the contact's primary or secondary identifier key(s). Default primary and secondary contact identifier keys can be configured uniquely for each Cordial account based on client's data infrastructure.
• A contact can have multiple contact activities documenting various action types.
• Actions taken within a message will automatically generate an activity record.
• Users can also create custom event activities such as "browse", "order", "clicked", etc.
• Custom event activities can be added and acted upon through contact activities records in the Cordial database.
• Contact activity data will be stored for 18 months, after which it will be systematically purged.

Resource Associations:

The following resource collections are associated to this collection.

POST /contactactivities

Parameters

* Required

Example JSON Requests

The following will create a new contact activity record for a user-defined "browse" event.

{
	"a": "browse",
	"email": "msmith@example.com",
	"ats": "2018-01-09 17:47:43",
	"properties": {
		"category": "Shirts",
		"url": "http://example.com/shirts",
		"description": "A really cool khaki shirt.",
		"price": 9.99,
		"title": "Khaki Shirt"
	}
}

Example Request URIs

The following URI in conjunction with the JSON will perform the POST.

http://<path>/contactactivities

GET /contactactivities

Parameters

* Required

Note: Get /contactactivities can process a maximum of 10k records. For example, a request for 1k records per page will return records for pages 1 through 10 but it will not return records on the 11th page. If it is necessary to access more than 10k contact activity records, the /contactactivityexport API endpoint should be used.

Example Request URIs

The following URI will retrieve all contact activities.

http://<path>/contactactivities

The following URI will retrieve all contact activities where the email address "msmith@example.com" is the contact identifier.

http://<path>/contactactivities?email=msmith@example.com

The following URI will retrieve all contact activities where the action is "browse".

http://<path>/contactactivities?action=browse

The following URI will retrieve all contact activities where the action is "browse" and email address "msmith@example.com" is the contact identifier.

http://<path>/contactactivities?action=browse&email=msmith@example.com

The following URI will retrieve all contacts but only include the contact activities that have occurred between the specified start date and end date.

http://<path>/contactactivities?time[between][start]=2018-01-01&time[between][end]=2018-01-03

The following URI will retrieve all contacts but only include the "open" contact activities that have occurred between the specified start date and end date.

http://<path>/contactactivities?time[between][start]=2018-01-01&time[between][end]=2018-01-03&action=open

The following URI will retrieve all contact activities starting from the 3rd page and grouping contact activities by 10 per page. For example, page 1 would have included the first 10, page 2 the second group of 10 and so on. Note: The default per_page value is 25.

http://<path>/contactactivities?page=3&per_page=10

The following URI will return a count of all contact activities in the request:

http://<path>/contactactivities?return_count=true