Go live with TFU Live agent
Switch the rep’s campaign on, as the dashboard’s Go live does: through the same campaign update, judged by the same go-live check. Use it only when the user asks for the rep to go live. While Check TFU Live go-live readiness lists anything, it is refused (422 TFU_LIVE_GO_LIVE_BLOCKED) with every blocker in blockers, in the words that check gives, and the campaign stays paused: clear them, then ask again. Going live adds no start rule, tag or number; the campaign starts doing what it is already set up to do. Once live, an outbound rep with start tags begins calling the contacts that match them, and an inbound rep only answers calls to its numbers, now as real calls. Asking again while it is live changes nothing (unchanged). Machine credentials use the returned tfu_live: agent id, and need agents:write as well, as every change to a TFU Live agent does.
Required scope: campaigns:write.
Required API key scope: campaigns:write.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Path Parameters
TFU Live agent id. Never use an ordinary provider agent id.
Query Parameters
Sub-account belonging to the authenticated agency and any narrower credential location binding.
When more than one campaign uses this rep, the one to switch. Without it, the rep’s first campaign, the one Check TFU Live go-live readiness reads.
^[a-zA-Z0-9_-]{1,100}$Body
Request payload. Detailed schema pending — see the route handler.
