MADIAD Hub publishes through each platform’s official API, using the OAuth flows those platforms approve. Nothing in the delivery path simulates a browser, borrows a login session, or routes through an intermediary account.
How a post reaches a platform
- Official APIs only. Every platform Hub supports is reached through its documented publishing API, under an application the platform has approved.
- You authorize your own account. Connecting a platform sends you through that platform’s own OAuth screen. Hub never asks for, stores, or replays your platform password.
- Payloads match platform requirements. Aspect ratio, caption length, file size, and per-platform options are adapted before the request leaves Hub, so a post is not rejected for a format the platform never accepts.
- Requirement changes are our maintenance, not yours. When a platform changes its API or its media rules, MADIAD updates the integration. Your integration keeps calling the same endpoint.
What you are responsible for
The content you publish and how often you publish it. Hub sends what you give it, to the accounts you connected, at the times you choose.
Hub guarantees the delivery method, not the content. Content that violates a platform’s policies, spam, or abusive behavior can still get a post removed, an account’s reach restricted, or an account suspended. That decision belongs to the platform and MADIAD cannot reverse it.
connection.reauth_required webhook. Reconnecting the account is the first step. If reconnecting succeeds and posts still fail, the restriction is on the platform side and has to be resolved in that platform’s own account tools. See Errors for the response shape and Webhooks for the event payload. 
