Skip to content
Fans API
[Scheduling API]

Give every scheduled action a clear next step.

Design scheduling workflows around drafts, account selection, review and request results. Explore platform guides and confirm supported publishing operations.

[FROM CONTEXT TO ACTION]

Build around a clear workflow.

Scheduling is a workflow with several states: draft, reviewed, queued and confirmed by the platform. Keep those states separate in your product. Use a documented scheduling operation where one exists; otherwise your application needs its own job queue and a supported publishing endpoint. These guides do not establish a universal FansAPI scheduling endpoint.

  1. 01

    Prepare the content

    Check the platform's supported formats, media requirements and text fields. Keep the selected account visible while the draft takes shape.

  2. 02

    Confirm the contract

    Read the publishing or scheduling operation. Check timezone handling, authorization and what the returned status actually means.

  3. 03

    Resolve the outcome

    Track the job through its request result. Make failures actionable and verify an uncertain outcome before retrying a publish request.

[DESIGNED FOR YOUR PRODUCT]

Make the details explicit.

Timezones and edits

Show the intended publication time with its timezone. Define how edits, cancellation and daylight-saving changes affect queued work.

Publishing confirmation

A queued job is not a published post. Use the documented response or status operation before displaying a completed result.

Retry behavior

Separate safe reads from write attempts. Keep a job identifier and request history so a transient failure does not create duplicate content.

[FAQ]

Before you build.

Scope, access and the first request.