✦ Partner API
How to fix plan_required 403 after a MultiPost API customer downgrade
Quick answer
When MultiPost returns 403 plan_required, pause Partner API publishing only for that tenant and route the customer to billing. Do not rotate a valid token or retry unchanged jobs; API publishing requires Pro or Agency. Recheck GET /api/v1/me and connected accounts before releasing the queue after canPublish becomes true.
How do you fix plan_required after a MultiPost customer downgrades?
Stop that tenant's Partner API sends and show a billing action whenPOST /api/v1/publish returns 403 plan_required. API publishing requires the linked MultiPost user to have Pro or Agency; retrying the unchanged request cannot bypass a Free plan.
Keep the customer's token and saved targets isolated but paused. A valid bearer token can still identify the user even when their current plan is no longer eligible to publish through the API.
What is the fast way to restore API publishing with MultiPost?
Send the customer to MultiPost plans and billing, then call GET /api/v1/me again and resume only when canPublish is true.
Refresh their connected accounts before releasing queued work so the request still targets the intended platform-and-handle pairs.
Which response distinguishes a plan downgrade from a revoked token?
A plan downgrade returns 403 plan_required, while a missing, invalid or revoked bearer token returns 401 unauthorized. Route the first to billing and the second to a secure token-replacement flow.
Follow the separate runbook for recovering a revoked MultiPost API token instead of asking every 403 customer to rotate credentials.
What should happen to queued tenant jobs during the billing pause?
Mark them blocked by plan and do not consume retry attempts against the same 403 response. Preserve their original content and targets, but require a fresh plan and account check before sending because the queue may outlive an account connection.
Use the fields described in the guide to check plan and monthly quota before each API call as the release gate.
How does MultiPost keep the billing boundary explicit?
MultiPost resolves the plan from the bearer token's owner and rejects API publishing before media preparation when the account is not Pro or Agency. Your SaaS turns that response into a tenant-scoped pause, a clear billing path and a verified resume.
Frequently asked questions
What does plan_required mean?
The bearer token identifies a user whose current MultiPost plan is not eligible for Partner API publishing.
Which plans can publish through the API?
MultiPost Partner API publishing requires Pro or Agency.
Should the customer replace their token after this 403?
No. Token replacement is for a 401 authentication failure, not a plan_required billing response.
When can queued jobs resume?
Resume after GET /api/v1/me reports canPublish true and the expected connected targets are still present.
✦ Start free
Turn a billing response into a safe tenant-scoped pause.
MultiPost exposes the current plan while your SaaS controls the billing path and verified resume.