Skip to content
Fans API
Bluesky

Workflow preview · Confirm Bluesky access with our team

Your Bluesky posts. Your voice, in context.

Bring a recognizable identity, rich text and post context into your app. Explore a Bluesky experience that keeps the person behind the post in view.

  • Account identity
  • Rich-text context
  • Post review

Join 100,000+ builders

[Why FansAPI?]

Keep identity attached to the idea.

Build an approachable writing flow while respecting the account and record model beneath it.

Fans APIPlan your social workspace
BlueskyUnderstand identity and records
Account identityKeep the author and handle visible beside the draft.
Account identityConfirm the account identifiers and authorization used by your connection.
Post contentReview the text and its destination links together.
Post contentBluesky posts are structured records; native text features need the correct representation.
ConversationKeep the original post close when preparing a response.
ConversationPreserve the record references needed for the intended action.
ResultShow the actual outcome of an authorized request.
ResultA local preview is not evidence that a record was created.

Fans API

Plan your social workspace
  • Account identityKeep the author and handle visible beside the draft.
  • Post contentReview the text and its destination links together.
  • ConversationKeep the original post close when preparing a response.
  • ResultShow the actual outcome of an authorized request.

Bluesky

Understand identity and records
  • Account identityConfirm the account identifiers and authorization used by your connection.
  • Post contentBluesky posts are structured records; native text features need the correct representation.
  • ConversationPreserve the record references needed for the intended action.
  • ResultA local preview is not evidence that a record was created.

Bluesky’s native capabilities do not establish FansAPI availability. Confirm the connection and supported operations separately.

[How it works]

From an identity to a post with context.

A clear path for the account, the message and the final review.

  1. 01

    Choose the identity

    Select the account and keep its handle visible. Confirm the authorization method for the intended integration.

  2. 02

    Prepare the post

    Write the text and review its links. Preserve the context behind any reply or reference.

  3. 03

    Review the record

    Check identity and content together. Keep a local preview distinct from an actual published result.

[Identity meets content]

A post with its context intact.

Bring the account and the message together, with links presented as part of the story.

Identity in view

Show the author and handle throughout the content preparation flow.

Text with meaning

Give links and mentions a deliberate representation instead of treating every post as plain text.

A considered link preview

Review where a link leads alongside the message that introduces it.

Record-aware context

Keep the references associated with a post or response in your application model.

Review before publishing

Put the intended identity, text and destination in one final check.

Private authorization

Handle account credentials on your server using the confirmed authentication contract.

[Make it part of your product]

Your stack. A familiar starting point.

Start with a server-side read request. Supply a confirmed Bluesky endpoint and its required header from your integration documentation. This HTTP template does not establish a FansAPI connection.

const response = await fetch(process.env.BLUESKY_API_URL, {
  headers: {
    [process.env.BLUESKY_AUTH_HEADER_NAME]:
      process.env.BLUESKY_AUTH_HEADER_VALUE
  }
});

const data = await response.json();
console.log(data);
TEMPLATEBLUESKY_API_URL · server environment
[Keep the model clear]

The author, the text and the reference.

Translate the content model into a readable application experience.

ContextInterface roleWhat to preserve
IdentityAuthor & handleThe account associated with the proposed post.
ContentPost textThe message and the intended link or mention semantics.
ReferenceConversation contextThe record relationship relevant to the selected action.
OutcomeConfirmed resultThe result actually returned by the integration.

The illustrated draft is not an AT Protocol record submitted to a server.

[Before you start]

Everything you need to connect.

Prepare the account and permissions your Bluesky workflow needs. Confirm the FansAPI connection separately.

  • An account and clear purpose

    Identify the Bluesky account and the specific reading or writing workflow your app needs.

  • A confirmed authentication method

    Check the supported authorization flow with FansAPI; do not assume public reads and account writes use the same access.

  • A record-aware backend

    Keep credentials private, preserve relevant record references and handle real request outcomes.

Match the plan to your workflow.

Review FansAPI plans, then confirm Bluesky availability, included operations and usage limits with our team. Native platform access, quotas and charges are separate; creating an account does not establish Bluesky access.

Explore pricing
[FAQ]

Building with Bluesky?

The essentials before your first request.

Bluesky

Build around the person behind the post.

Start shaping your social experience. Confirm Bluesky access and supported operations with our team.

  • Identity
  • Content
  • Context