List
Read a page of communications. Control what is returned via the properties query param.
Query parameters
The paging cursor token of the last successfully read resource will be returned as the paging.next.after JSON property of a paged response containing more results.
Whether to return only results that have been archived.
A comma separated list of object types to retrieve associated IDs for. If any of the specified associations do not exist, they will be ignored.
The maximum number of results to display per page.
A comma separated list of the properties to be returned in the response. If any of the specified properties are not present on the requested object(s), they will be ignored.
A comma separated list of the properties to be returned along with their history of previous values. If any of the specified properties are not present on the requested object(s), they will be ignored. Usage of this parameter will reduce the maximum number of communications that can be read by a single request.
Response
successful operation
Example response
{
"paging": {
"next": {
"after": "NTI1Cg%3D%3D",
"link": "?after=NTI1Cg%3D%3D"
}
}
}Changes
Changed in 10 of the 55 revisions of this API.3112
- ○
endpoint added
endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
endpoint added
endpoint-added
This revision also has 9 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
- ▲
- ○
added the optional property
//to the response with the statusresponse-optional-property-added
- ○
- ▲
removed the required property
//////from the response with the statusresponse-required-property-removed
- ●
removed the optional property
//////from the response with the statusresponse-optional-property-removed
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
the response property
//////became required for the statusresponse-property-became-required
- ○
- ○
added the optional property
//////to the response with the statusresponse-optional-property-added
- ○
added the optional property
//////to the response with the statusresponse-optional-property-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ○
the endpoint scheme security
app_cookiewas removed from the APIapi-security-removed
- ○
the endpoint scheme security
hapikeywas removed from the APIapi-security-removed
- ○
the endpoint scheme security
internal_cookiewas removed from the APIapi-security-removed
- ○
the endpoint scheme security
private_appswas removed from the APIapi-security-removed
- ○
the endpoint scheme security
shhkeywas removed from the APIapi-security-removed
- ○
- ○
endpoint added
endpoint-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○