API Access for AI Agents and Bots
Ai social poster is a preview/beta, safety-gated product. This page explains planned API access controls for reviewers and customers. API access cannot bypass provider review, customer consent, billing rules or publishing safety gates.
What Ai social poster does
Ai social poster helps customers and approved automation tools prepare drafts, platform payload previews and approval queue items. API access is planned for controlled draft and preview workflows before any customer-approved publishing workflow is considered.
Why permissions are requested
- Authenticate customer-controlled API requests for draft and preview workflows.
- Associate requests with a customer workspace, connected destination and audit trail.
- Apply provider review, usage, approval and safety checks before any downstream action.
- Let customers revoke automation access without exposing provider tokens or secrets.
What data may be accessed
- Workspace identifier, API key label, created date, last-used metadata and revocation status.
- Customer-submitted draft text, media references and platform payload preview data.
- Connected destination identifiers needed to validate that a request belongs to the customer workspace.
What data is not accessed
- API keys cannot access raw OAuth tokens, bot tokens, provider secrets or passwords.
- API keys cannot connect new social accounts without the customer's provider consent workflow.
- API keys cannot bypass provider review, customer approval, billing checks or safety gates.
- No real API key is generated from this documentation page.
How users connect accounts
Customers connect social destinations through provider-specific workspace flows. API access can reference only destinations already connected by the customer and only after the relevant provider review and safety requirements are met. Future API key creation is expected to require a minimum balance of $5.
How users disconnect accounts
Customers can revoke API keys and disconnect provider destinations from the workspace when those controls are enabled. Revoking a key prevents new API requests from that key. Disconnecting a destination prevents API workflows from using that destination.
Publishing approval and safety gates
Live publishing remains blocked in this preview documentation state. Future API-driven publication requests are planned at $0.04 per publication, but billing and publishing cannot proceed unless customer approval, provider review, connected destination checks, credit checks and internal safety flags all allow the action.