✦ Partner API
How to handle partial failures from a multi-target social publishing API
Quick answer
Handle a partial social-publishing failure by inspecting every MultiPost target result, storing successful network IDs and retrying only failed platform-and-handle pairs after fixing their cause. Check the linked user’s plan, quota and current accounts before retrying; never replay all targets when some may already be public.
How should a SaaS handle partial failures from a multi-target social publish request?
It should evaluate every item in the results array, persist successful target IDs and retry only failed destinations after diagnosing their errors. A multi-target response can report success for one network and failure for another, so the top-level status is not enough for safe retry logic.
Never replay all targets automatically after an ambiguous network error. The successful posts may already be public and a blanket retry can create duplicates while consuming additional quota.
What is the fast way to make MultiPost results observable?
The fast way is to log one record per platform and handle, including the request correlation ID from your system, MultiPost result ID, success flag and bounded error text. The user can review successful publications while your integration keeps its own operational history.
Check GET /api/v1/me before any manual retry and send users to MultiPost billing when the error ismonthly_limit. API calls cannot bypass plan enforcement.
Which errors should be fixed before a target is retried?
Authentication, missing media, unsupported type, invalid targets, excess slideshow images and unavailable media must be corrected before retrying. A plan-required or monthly-limit result needs an account or billing change, not a faster retry loop.
For account-specific failures, refresh the current list and ask the user to reconnect if necessary. The guide to secure multi-account scheduling explains the underlying OAuth boundary.
How do you build a retry request without duplicating successful posts?
Build a new target array containing only the failed platform and handle, then reuse the approved content after confirming it is still current. Record the relationship between the original operation and the retry so support can reconstruct what reached each network.
Remember that every successful network send counts separately. Use the multichannel quota calculation guide when estimating retry capacity for a high-volume integration.
How does MultiPost support a reliable partial-failure runbook?
MultiPost returns target-level outcomes and preserves successful publishes in the user's history, giving your SaaS enough information to separate delivery from recovery. Your runbook should classify the error, protect successful targets, check plan and account state, retry narrowly and show the final destination status to the user.
Frequently asked questions
Can one target fail while another succeeds?
Yes. MultiPost returns a separate outcome for every requested platform and handle.
Should I retry the entire request?
No. Protect successful results and build a new request containing only corrected failed targets.
What should I do with a monthly_limit error?
Check the user’s usage and plan; repeated calls cannot bypass server-side quota enforcement.
Where can the user verify successful publications?
Successful sends are saved in the linked user’s MultiPost Publications history.
✦ Start free
Recover failed destinations without replaying successful ones.
MultiPost returns per-target outcomes so your SaaS can retry narrowly and report clearly.