Preview removing an account
What removing the account would do to the posts that use it, counted now, with nothing changed: show it to the person before they confirm. Remove an account answers the same counts once it is done.
apiKeyAuthorizationBearer <token>An API key from the web app, under Developers. It starts with rz_live_.
id*stringThe account's id (acc_).
length <= 100OK
application/json- response
posts*By the post's status now.
curl -X GET 'https://api.rizamo.com/v1/accounts/acc_01m44bet40enpr62nh6w01e67r/removal'{ "posts": { "scheduled": { "posts": 2, "movedToDeleted": 1 }, "drafts": { "posts": 1, "movedToDeleted": 1 }, "published": { "posts": 14, "movedToDeleted": 6 }, "failed": { "posts": 0, "movedToDeleted": 0 } }}Search music for an account GET
Tracks the account may put on a post, from its network's library. TikTok: its Commercial Music Library's trending list (up to 100), filtered by genre, country and period; there is no search. The same filters answer the same list for 30 minutes, and searches beyond Rizamo's limits on TikTok answer 429 with when to try again. Instagram (accounts connected through Facebook Login): a search with `q`, or what is trending without it, up to 25, music or original sounds. Facebook adds no music through its API. A filter of the other network is refused. Attach a track's `id` in the target's `music` option.
Get a link to connect an account GET
A link to send a person to within 30 minutes: it goes straight to the network, and connects accounts once (a preview or a second browser that opens it uses nothing up). They log in on the network, with no Rizamo account, and come back to `redirectUrl`, or, without one, land on a Rizamo page that says what was connected (for a chat agent, a script or n8n). `instagram` is Instagram Login, for an Instagram professional account on its own; `facebook` is Facebook Login, its Pages and the Instagram accounts linked to them, which can also add music to reels and get each story's final numbers when it ends (deleting Instagram posts will need it too, once Meta reviews Rizamo's access). A login that reaches one new account the key may add connects it at once; one that reaches several (Pages, YouTube channels), or an account already in the team, shows the person a page to pick them, with only new accounts ticked. An account already in the team in a profile the key does not reach is never added. With `connectionId`, only that login's accounts are renewed. Back at `redirectUrl`, Rizamo adds `status` (connected or error), `network`, `profileId`, and either `accountIds` with each one's `billing` in the same order, comma-separated, or `error` (cancelled, refused, no_accounts, expired, used, unavailable, forbidden, gone, failed) and `message`. Nothing in it works without your key: read the accounts with `GET /accounts/{id}`. A return can arrive more than once (a reload): take `GET /accounts` (`list_accounts`) as the truth. A link opened once it is used or expired, or after your key lost access, stays on a Rizamo page that says why: only a person back from the network comes to `redirectUrl`. Accounts are billed as in the web app: the first 2 free. On the free plan the rest arrive `awaiting_payment` until an owner starts a plan. On a paid plan they are charged at once to the card on file: your call is the consent. A charge that needs the card holder, or more accounts than the owner lets the API add this period, leaves them `awaiting_payment` until an owner pays in the web app. The person connecting never sees prices. With `connectionId`, the person logs in again for that login's accounts (an expired login): only accounts already in the team are updated, and `network` must be the login's.