How to check plan and monthly quota before a social publishing API call

Call GET /api/v1/me with the customer's bearer token before enabling a publish action. Continue only when canPublish is true and usage.remaining is either a positive number ornull, which represents an unlimited Agency allowance.

Treat the response as a fresh preflight signal, not a quota reservation. Every successful network send consumes one unit, so a request with three targets can require three available units by the time it runs.

Have the customer connect social accounts in MultiPost, store their personal API token on your server and call/api/v1/me before listing accounts or sending content.

Partner API publishing requires Pro or Agency. Send customers to MultiPost plans and billing whencanPublish is false or their paid allowance needs attention.

Use plan, canPublish, usage.used,usage.limit, usage.remaining andconnectUrl. Render a clear disabled state for Free and a target-aware warning when a finite remaining balance is too small.

A null limit or remaining value means unlimited, not missing data. The broader guide to adding social publishing without provider OAuth tokens shows where this check fits in the tenant flow.

No. MultiPost enforces plan and quota again on the server when it handles the publish request, and individual networks can still reject a target. Another request for the same customer may also consume units between the check and the send.

Always inspect each returned result and persist successful platform IDs. If some targets fail, follow the partial-failure retry workflow instead of replaying the full request.

MultiPost resolves the plan and monthly usage from the bearer token's owner and applies the same server-side rules to Partner API sends. Your SaaS should use preflight for user experience and still treat the publish response as the final decision for every target.