Accounts
Status: Current (Scale plan). An account is a social handle registered so runs can target it. Every run and schedule names anaccount_username; the platform a run executes against is resolved from this roster at dispatch, never from the API caller.
All paths are relative to <baseUrl>/v1 and require Authorization: Bearer. Reads need accounts:read; writes need accounts:write.
Credentials and proxies are never accepted over
/v1 — you register only the handle. Login state and per-account proxies stay on your Mac, where your own connected iPhones execute the work (bring-your-own-fleet).Endpoints
Register an account — POST /v1/accounts
Returns
201 with { "account": Account }. A handle already registered on that platform returns 409 conflict; an invalid platform or username returns 422 invalid_request.
X accounts need one more step: the operator must set the target app in Warmr’s Settings on the Mac before X runs will execute. TikTok and Instagram accounts always resolve from the roster. See Runs → target app resolution.
List accounts — GET /v1/accounts
Returns { "accounts": Account[] }, org-scoped by row-level security — you only ever see your own org’s handles.
The Account object
Next
- Runs — enqueue a warm_up or post against a registered account.
- Content uploads — stage a clip to post.
- SDK quickstart — register, enqueue, and post end to end.