GET Get Subscriber Message Logs​
Paginated message history of one contact on one channel, for the contact-profile SMS / WhatsApp tabs. It reads the contact's thread on the channel; a contact never messaged on that channel simply gets an empty list. Rows are sorted by the effective time (sent_at, else scheduled_at, else created_at) then ID, in order. A missing contact returns HTTP 422 with code: 404 in the body (the controller passes 404 inside the payload, not as the HTTP status). Replaces GET /sms/subscribers/{id}/logs. PRO (FluentCampaign Pro Messaging module).
Required capability: fcrm_read_emails or fcrm_manage_emails — which one applies depends on the action being performed.
Enforced by MessagePolicy::verifyRequest(), the policy default for this route group.
Requires: FluentCampaign Pro with the Messaging module enabled. While no messaging channel (SMS or WhatsApp) is switched on the route is not registered at all and returns a 404.
Authorizations​
WordPress Application Passwords — use Basic auth with your WordPress username and an application password in the format: username:application_password
Parameters​
Path Parameters
Subscriber (contact) ID.
Query Parameters
Channel to scope the request to. Unknown or missing values fall back to sms.
"sms""whatsapp""sms"campaign or automation (by ref_type), incoming (inbound), or custom_sms (outbound with no campaign/automation ref). Any other value behaves like custom_sms; all disables filtering.
"all""campaign""automation""incoming""custom_sms""all"Sort direction. Anything other than desc sorts ascending.
"asc""desc""asc"Page number.
1Rows per page (not clamped).
20Responses​
Paginated message logs.