Conversation history
Keep message identifiers and account context together. Handle unavailable or deleted messages without losing the rest of the thread.
A reply needs more than a text box. Keep the sender, recipient and recent conversation visible from the first draft through the request result. FansAPI's creator references document account-specific conversation operations. WhatsApp, Telegram and Instagram guides describe separate workflows whose access and messaging contracts must be confirmed for your integration.
Attach the business or creator identity to the conversation. Verify the recipient and the account's permitted operations.
Keep recent messages beside the draft. Let the person reviewing it check the recipient, tone and final copy before sending.
Use actual request results and supported events to update the conversation. Distinguish a saved draft from a submitted or delivered message.
Each guide keeps its own scope and access requirements. Workflow previews are identified on the destination page.
Keep message identifiers and account context together. Handle unavailable or deleted messages without losing the rest of the thread.
Consent, messaging windows, templates and media support differ by channel. Read the applicable platform requirements before enabling a send action.
Give your team a clear review step. If a request is retried, check the previous result to avoid sending the same message twice.
Scope, access and the first request.
Explore social media API workflows for accounts, content, conversations and reporting. Find the platform guide and reference for the integration you want to build.
Plan account reporting and attribution workflows with FansAPI. Explore creator earnings, Smart Link conversions and platform-specific reporting requirements.
Design scheduling workflows around drafts, account selection, review and request results. Explore platform guides and confirm supported publishing operations.