Publish to multiple accounts safely
Target several profiles, pages, channels, or boards while preserving account-specific validation and results.
Place every selected account ID in target_account_ids and keep account-level overrides limited to content that genuinely differs. Validate the target set before creation and reconcile each returned target instead of assuming identical provider behavior.
What this means in practice
Place every selected account ID in target_account_ids and keep account-level overrides limited to content that genuinely differs. Validate the target set before creation and reconcile each returned target instead of assuming identical provider behavior.
Use the documented brand and account boundaries consistently across the scheduler, REST API, SDK, MCP tools, SSE consumers, and webhooks. That makes the same social operation explainable to an operator and reproducible by an integration.
Implementation checklist
Confirm every account belongs to the selected brand and is active.
Group accounts by capability, locale, audience, and approval ownership.
Use common content as the baseline and account-specific overrides only where needed.
Preview all targets and surface failures next to the account that caused them.
Report delivery and credit settlement per target account.
Operational details
A single provider may expose pages and personal profiles with different permissions.
One-time multi-account scheduling is part of V1; evergreen and recurring campaigns belong in a consuming CRM or automation system.
Account selection should remain stable between preview and create, or the client should preview again.
Common mistakes to avoid
- Do not hide an account-specific warning behind a campaign-level success message.
- Do not assume the same media crop, title, or destination is valid for every account.
- Do not duplicate successful remote posts when only one target needs retry.