How to run multiple branded social accounts from one REST API

The hard part of running social accounts at scale was never the posting — it's the operations underneath it: sourcing devices, keeping SIMs alive, branding each profile, warming them, and doing it again every time an account dies. Attention Factory turns that operations problem into a REST API. Here's the whole flow.

The base URL is https://api.attentionfactory.com and every request is authenticated with a bearer key:

Authorization: Bearer af_live_...

1. Rent an account

One call provisions a real US account on the platform you name, branded and warmed to your niche before it goes to work. You can hand it a warming niche and initial branding in the same request:

POST /v1/rentals
{
  "platform": "tiktok",
  "auto_renew": true,
  "warming_niche": "fitness",
  "branding": { "display_name": "Maya Fields" }
}

Do this thirty times (or loop it) and you have a fleet. Each rental comes back with an id you'll use for everything else. Pricing is flat — a single monthly rate per account with no per-action fees — so a fleet's cost is predictable regardless of how hard you drive it.

2. Brand it

Branding is a separate endpoint so you can update it any time, not just at creation. The fields each platform accepts differ — Instagram takes a username, bio, and category; LinkedIn takes a headline and summary instead of a bio — and the API only accepts what's valid for that platform:

POST /v1/rentals/{id}/branding
{
  "display_name": "Maya Fields",
  "username": "maya.trains",
  "bio": "Strength & mobility. Coach. Austin, TX."
}

Good branding is what makes thirty accounts read as thirty distinct people instead of thirty clones — different names, photos, bios, and niches.

3. Let it warm

If you set a warming_niche at rental time, warming is already running. You can also enroll or change it explicitly:

POST /v1/rentals/{id}/warming
{ "niche": "fitness" }

Warming takes days, not minutes — the account builds real history and a relevant graph on its device before you ask it to do anything commercial. Poll the rental's status; when it flips from warming to active, it's ready.

4. Drive activity

Once an account is active, everything you'd do by hand becomes a call — posts, comments, DMs, follows, stories:

POST /v1/rentals/{id}/{platform}/actions
{
  "type": "post.video",
  "params": { "video_url": "https://cdn.example.com/clip.mp4", "caption": "3 drills for hip mobility" }
}

Each action is dispatched to the physical device and executed in the native app. Because pricing is flat, you can call this as often as your strategy needs — a hundred posts across the fleet costs the same per account as ten.

Wiring it together

The pattern for a fleet is a simple loop plus a wait:

1. POST /v1/rentals per account, with a niche and starter branding.
2. Poll each rental until status === "active".
3. Fan your content out across the fleet via the actions endpoint.
4. Subscribe to webhooks (rental.active, action.verified) instead of polling if you'd rather be pushed.

That's a fleet of real, branded, warmed accounts running from code — no hardware, no per-action metering. The full endpoint reference, including per-platform action types and branding fields, lives in the docs.