Test a comment automation
Whether a comment with this text would trigger it, and the messages it would send, with their Rizamo links: each as its text and its button (the link, or the follow gate's reply button). Nothing is sent or recorded. Whether the person already got it, follows the account or is within Meta's windows is only known for real comments.
apiKeyAuthorizationBearer <token>An API key from the web app, under Developers. It starts with rz_live_.
id*stringThe comment automation's id (cauto_).
length <= 100Idempotency-Key?string1 to 255 printable characters, new for each request (a UUID); the body up to 1 MB. For 24 hours a repeat with the same key, path and body gets the first answer, with Idempotent-Replayed: true, instead of running again; 5xx, 409 and 429 answers are not kept. Errors, Retries, has the rest.
1 <= length <= 255application/json- body
text*stringA sample comment.
length <= 2200OK
application/json- response
triggers*booleanreason*stringWhy it would or would not answer, in a sentence.
keyword*|The keyword that matched.
privateReply*|The first private reply, as it would go out: the message with its Rizamo links, or the follow gate's ask.
afterFollow*|Follow gate: the message sent once they reply as a follower.
reminder*|Follow gate: sent once if they reply without following.
publicReplies*array<string>One of these is posted under the comment, at random, after the private reply.
markDone*booleancurl -X POST 'https://api.rizamo.com/v1/comment-automations/cauto_01m4h40hg0f4wa1w5cfcgpjrp3/test' \ -H 'Idempotency-Key: 4b9e7c1a-2f3d-4e8a-9c6b-1d2e3f4a5b6c' \ -H 'Content-Type: application/json' \ -d '{ "text": "Menu please!"}'{ "triggers": true, "reason": "It has the keyword menu, as a whole word.", "keyword": "menu", "privateReply": { "text": "Here is our winter menu, with every drink and pastry of the season.", "button": { "title": "See the menu", "url": "https://go.rizamo.com/w2Lp9d" } }, "afterFollow": null, "reminder": null, "publicReplies": [ "Sent it to your messages!", "Check your DMs!" ], "markDone": true}List a comment automation's runs GET
One run per matched comment, newest first, a page at a time: pass `nextCursor` as `cursor` for the next one. A run stays when its comment is deleted, but its `threadId` may then be gone from the inbox, and a private reply not sent yet is skipped (`refused`).
Analytics overview GET
The numbers of the team's accounts and of every post on them, made in Rizamo or anywhere else, for a period and the one before it: views, reach, engagements, the engagement rate of the posts published, posts published, followers, the accounts' own reach and accounts engaged, each day, each network, and the top posts. A period of `days` ends yesterday, the last complete day, as `to` does when left out. With `attribution` received (the default), views are each account's own views of each day, as its network counts them (its posts' gains where its days give none, and with `fields`), and reach and engagements what arrived on the posts in the period, on posts of any age, by the day it arrived; with publish, they are the numbers so far of the posts published in the period, by the day each went out. A number a network does not give is missing, never 0, and `notes` says why. Post numbers follow the days of the profile's time zone (pass `timeZone` for another); followers and the accounts' own numbers come by the network's days, matched by date (Meta's run on Pacific time, TikTok's on UTC). TikTok's days come 2 days late and YouTube's 3.