Endpoint ·
GET /quick-repliesRead-only endpoint: it returns information and changes nothing. It is not sent inside the
actions array — you call it directly.name, and that is the value you later pass
in quick_reply.name when assembling a send action. The catalog does not expose
the quick reply content (the shape of its actions is not included): it is
meant to discover which names exist, not to inspect what each one sends.
Parameters
slug— business slug in the path, case-insensitive. It must match the token’s business. Required.search— name substring, case-insensitive (1 to 100 characters). The asterisk*works as a wildcard and matches any sequence of characters; the%and_characters are matched literally. Optional.cursor— opaque cursor returned by the previous page innext_cursor. Omit it to request the first page. Do not reuse cursors across different endpoints: even though the format is identical, each endpoint interprets it over its own data set. Optional.limit— quick replies per page. Defaults to 20, maximum 100. Optional.
Response
has_more tells you whether there are more results after this page. While it is
true, repeat the call passing the next_cursor value in ?cursor= and
keeping the same filters. When has_more is false, next_cursor comes back
as null.
Example
This is a pure read: it asks for the first page of the catalog to see which names are available. The call sends no message and modifies no conversation — it only returns names, which then feed a send action.Errors
See the full catalog in Errors.
The
name this query returns is exactly the one consumed by the send actions:
Send message in quick reply mode
(quick_reply: { "name": ... }) and Send quick reply or
template, which sends the quick
reply when the 24h window is open and the template when it is closed. The name
is matched case-insensitively, but it is best to copy it exactly as the catalog
returns it.