Read one text
get_site_message_send
Reads one text in full, with every delivery update.
It has the text that went out, with a verification code masked, the value of each placeholder, the credits it cost, the part the plan's included credits paid (includedCredits) and whether they came back, its parts, the template name it went out under and why it failed when it did. cancellable says whether cancel_site_message_send can still stop it.
Request
Call it with a POST to https://api.modulify.ai/v1/get_site_message_send, sending the inputs below as a JSON object. The token needs the config:read scope.
It only reads and changes nothing, so retrying it is safe.
curl -X POST https://api.modulify.ai/v1/get_site_message_send \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"projectId":"PROJECT_ID","sendId":"SEND_ID"}'Over MCP, the same method is the get_site_message_send tool.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
projectId |
string | Yes | The site id. |
sendId |
string | Yes | The text id, from list_site_message_sends. |
Response
Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.