Skip to main content
GET
Search CannedResponses
A CannedResponse, also called a message macro, is a reusable CRM message template owned by a location and identified by a required name, optional subject, and optional HTML body.

Authentication

This endpoint requires OAuth2 authentication. Include a valid bearer token in the Authorization header. The authenticated user must be a full unrestricted administrator or have the CannedResponse-List role.

Query Parameters

Pagination & Sorting

integer
default:"1"
The page number to retrieve.
integer
default:"25"
The number of records per page.
string
The property name to sort results by (e.g. Name, CreatedOn).
integer
Sort direction. 0 for ascending, 1 for descending.

Filters

integer
Filter by iD of the location that owns this message macro; the user must have access to the location.
string
Filter by display value for Business.Name..
string
Filter by required name used to identify this reusable message macro.
string
Filter by optional subject line for the message macro.
string
Filter by optional HTML body content for the reusable message macro.

Range Filters

string
Filter records created on or after this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records created on or before this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records updated on or after this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records updated on or before this date. Format: YYYY-MM-DDTHH:mm.

Code Examples

Simple listing

Filtering by Name

Range filters

Response

200

CannedResponse[]
The list of CannedResponse records matching the query. See the Get one CannedResponse endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each CannedResponse. The following fields are not populated in the Records[] response: MessageText.To get all fields, fetch the full record using the Get one CannedResponse endpoint.Important for updates: When updating a record via PUT, always retrieve the full record with a GET request first, apply your changes to that complete data, and then send the updated record. Do not use data from a listing response as the base for a PUT request, as missing fields may be unintentionally cleared.
integer
Current page number.
integer
Number of records per page.
string
The field used for sorting.
integer
The sort direction (0 = ascending, 1 = descending).
integer
Index of the first item on the current page.
integer
Index of the last item on the current page.
integer
Total number of matching records across all pages.
integer
Total number of pages.
boolean
Whether there is a next page of results.
boolean
Whether there is a previous page of results.
Example Response