Skip to content
Fans API
WhatsApp

Workflow preview · Confirm WhatsApp access with our team

Your WhatsApp conversations. Part of your product.

Bring the business, the message and the next step into one thoughtful workflow. Explore how WhatsApp conversations could fit into your app.

  • Business context
  • Message preparation
  • Conversation flow

Join 100,000+ builders

[Why FansAPI?]

Keep the conversation connected.

A clear place for your application experience, and a clear boundary for the platform connection.

Fans APIPlan your application workflow
WhatsAppConfirm the connection
Business identityKeep the selected business visible throughout the conversation.
Business identityCheck account eligibility, phone-number setup and required permissions.
Message preparationBring recipient context, message copy and review into one flow.
Message preparationConfirm supported message types and any template requirements.
Conversation stateMake drafts, pending requests and delivery updates easy to distinguish.
Conversation stateUse the documented response and event contract for each operation.
CredentialsLet your interface work through your own backend.
CredentialsKeep tokens private and confirm the access your integration requires.

Fans API

Plan your application workflow
  • Business identityKeep the selected business visible throughout the conversation.
  • Message preparationBring recipient context, message copy and review into one flow.
  • Conversation stateMake drafts, pending requests and delivery updates easy to distinguish.
  • CredentialsLet your interface work through your own backend.

WhatsApp

Confirm the connection
  • Business identityCheck account eligibility, phone-number setup and required permissions.
  • Message preparationConfirm supported message types and any template requirements.
  • Conversation stateUse the documented response and event contract for each operation.
  • CredentialsKeep tokens private and confirm the access your integration requires.

FansAPI WhatsApp availability is under review. This page describes a proposed workflow, not a live messaging connection.

[How it works]

From business context to a better reply.

Three moments that keep a conversation clear, from the first selection to the next action.

  1. 01

    Choose the business

    Start with the right business identity. Keep the destination visible as your team prepares a conversation.

  2. 02

    Prepare the message

    Bring recipient context and message copy together. Review the content and applicable messaging requirements.

  3. 03

    Follow the conversation

    Keep each reply in context. Once connected, use actual API responses to show what needs attention next.

[Designed around the conversation]

Every message needs a little context.

A focused interface for the people, messages and next steps in your WhatsApp workflow.

The right business

Make the sender identity clear before anyone starts writing a reply.

A considered message

Give your team space to write, check and refine a message before sending.

Conversation context

Keep the latest message close to the reply so the conversation stays easy to follow.

Review before action

Check the recipient and message together. Keep drafts separate from submitted requests.

Clear request states

Design distinct pending, delivered and failed states, driven by confirmed API results.

Private credentials

Keep secrets on your server and expose only the information your interface needs.

[Make it part of your product]

A familiar place to start building.

Use this server-side HTTP pattern with a confirmed read endpoint and its required headers. WhatsApp-specific endpoints and payloads will depend on the final FansAPI contract.

const response = await fetch(process.env.WHATSAPP_API_URL, {
  headers: {
    [process.env.WHATSAPP_AUTH_HEADER_NAME]:
      process.env.WHATSAPP_AUTH_HEADER_VALUE
  }
});

const data = await response.json();
console.log(data);
TEMPLATEWHATSAPP_API_URL · server environment
[Keep each state clear]

One conversation. A clear next step.

Separate the state of your interface from the result of a network request.

MomentInterface stateWhat it means
Writing a replyDraftThe message is being prepared. No request has been sent.
Reviewing contentReady for reviewThe recipient and message are ready for a final check.
Awaiting a resultPendingA request was submitted. Wait for the actual response or event.
Handling an updateDelivery updateShow the reported result and a useful next action if attention is needed.

These are interface labels, not WhatsApp or FansAPI response-field names.

[Before you start]

Everything you need to connect.

Confirm availability and account requirements before connecting a business or choosing a plan.

  • An eligible business account

    Meta’s Cloud API uses a business portfolio, WhatsApp Business Account and business phone number. Confirm the requirements for your intended integration.

  • A confirmed integration contract

    Ask our team about WhatsApp access, authentication, supported operations and event delivery before implementation.

  • Your application backend

    Store credentials securely and handle authenticated requests on the server. Keep the frontend focused on the conversation.

Confirm the scope. Then choose a plan.

FansAPI plans are listed on the pricing page. WhatsApp inclusion, limits and any platform charges must be confirmed separately; a subscription does not establish WhatsApp access.

Explore pricing
[FAQ]

Building with WhatsApp?

The essentials before your first request.

WhatsApp

Make room for the next conversation.

Tell us what you want to build. We’ll help you clarify WhatsApp availability and the right next step.

  • Your business
  • Your app
  • Your workflow