Message log in the API

Feature

Week of September 29, 2026

The Message Log from Operations can now be pulled through the Stoked API, so delivery problems can feed your own alerts and dashboards instead of being spotted by hand.

GET /message_log — one record per message, with its channel, direction, what triggered it (a relayed text, a reminder, a verification code), its delivery status and the provider’s error code when delivery failed, and every status timestamp. Each record links to the advocate or prospect it concerns and to its conversation. Filter by status, channel, direction, trigger, conversation, advocate or prospect, or sync incrementally with filter[updated_since], which picks up a message whose status changed since your last run.
Imported history from before Stoked kept its own log is included and labelled backfilled, so the record is complete.
A new message_log permission gates the endpoint. Phone numbers and email addresses need message_log:pii as well. Both are off on every existing key until you tick them under Settings > API Keys. Message text is never served.

Related: Message Log API