The same publishing rules, for your own tools
Every member can hold a personal API key limited by their role. Keys are shown once, stored as a hash, and never include a social network token.
What you can call
List social accounts and their health, create a post, and read its status. Scheduling, analytics scopes and webhooks follow the organization plan.
Webhooks
Organization endpoints receive signed events for publish results and reconnects. Deliveries are logged. The signing secret is stored encrypted.
Docs in the account
Open API reference after you sign in. Connect itself stays in the browser, because each network has to approve access itself.