Changelog

POST /api/v1/messages/send-interactive sends messages the user answers with a tap, with one request shape on WhatsApp, Instagram and Messenger: reply and link buttons, cards with an image, title and buttons that scroll as a carousel, quick-reply chips on Instagram and Messenger, and lists on WhatsApp. Each channel gets its native message; a shape a channel does not have is refused with a clear 400 instead of being replaced by something else. Available on Pro, inside the 24-hour window. Docs: Sending Messages

A tap on a button, quick reply, list row, template button, menu item or ice breaker still arrives as message.received of type: "text" with the label as text, and now also carries button_id — the id you set, or the payload configured for the button elsewhere. Quick-reply buttons of WhatsApp templates take that id when sending, in variables.buttons. Docs: Receiving Messages

When Meta's conversation routing gives conversations to another app, Meta's inbox or Meta AI, replies through Fiwano are rejected for them. The channel page in the portal now shows this as a notice — whether the account sends new conversations to another app, or only some conversations are temporarily handled elsewhere — instead of frequent emails about each such incoming message. A reply that Meta rejects is still reported as before. Docs: Channels

Templates with an image, video or document header can now be sent through the API: pass the file in header_media_url. Authentication templates with a copy-code button can be created through the API and the portal, and are sent with the code given once. Template details now include Meta's rejected_reason and quality_score, status updates from Meta are improved, and a few edge cases of template handling are refined. The sync parameter of the template list is no longer needed and has no effect. Docs: WhatsApp Templates

On Instagram and Messenger shares (type: "share"), caption now means the same as on media: the text the user wrote together with the share, if any. Until now it could also carry the shared post's own caption, so the author's words and the user's words were indistinguishable, and a user's text sent with a captioned post did not arrive. The shared post's caption is no longer included; share.url links to the post. Docs: Receiving Messages

Every channel in GET /api/v1/channels now carries health: status is ok, or action_required when Meta no longer lets Fiwano work with the account or number — access or a permission revoked, a WhatsApp number removed or not on the Business Platform, an account blocked by Meta. reason is Meta's error with its code, since is when it was detected. In the portal, each channel has a Delivery problems page for the last 7 days: messages waiting for a retry or failed, with Meta's code and text, and webhook deliveries to your endpoint that are retrying, failed or recovered, with your endpoint's error. Docs: Channels

message.failed is now available on Instagram and Facebook Messenger. On every channel it also reports messages that were answered queued and could not be delivered after all — the retries ran out, Meta rejected the message on a retry or never confirmed it, or the channel was disconnected while the message waited. The payload is the one WhatsApp already uses: error is a short text reason, always present; errors is an array with Meta's full error details — code, title, message — included when Meta caused the failure. Add message.failed to webhook_events to receive it. Docs: Receiving Messages

The API now also accepts your key as Authorization: Bearer <key>, for tools and connectors that only support bearer tokens. X-API-Key stays the primary header and wins when both are sent. Docs: Authentication

The OpenAPI spec (/api/v1/openapi.json and .yaml) can now be imported by URL from browser-based tools, such as the API import in AI app builders. Docs: AI app builders

Support requests are now tracked in your Fiwano account. Write to us via Contact in the portal or email support@fiwano.com from your account address: each request becomes a ticket in the portal, with its current status and the full conversation history.

Small improvements to the connect flow for WhatsApp, Instagram and Messenger: clearer status next to the connect button, and trying again after closing Meta's window now works reliably. Docs: Channels

All public API operations except sending messages are now limited to 20 requests per second per API key. It is a guardrail against runaway loops, not a quota: normal integrations stay far below it. Exceeding it returns 429 with Retry-After, like the per-channel send limit. Docs: Capabilities

When a conversation starts from a Click-to-WhatsApp, Click-to-Instagram or Click-to-Messenger ad, or from an m.me / ig.me link with a ref parameter, Meta attaches attribution to the first inbound event. Fiwano now passes it on as data.referral on that message.received: source (ad, link, product), text (the ad copy the user saw), image_url (the creative, or a video's thumbnail), your ref, and raw — Meta's attribution object exactly as received, with the ad id, ctwa_clid for the Conversions API and the WhatsApp welcome message. On Instagram and Messenger the new opt-in event conversation.referral tells you when a returning user clicks an ad or a link into an existing conversation without writing; the click reopens the 24-hour window. The feature ships as a beta, which we expect to run until November 2026: the four normalised keys and the conversation.referral event may be adjusted, raw stays as it is. If you plan to rely on the normalised keys or on conversation.referral, tell us at contact@fiwano.com: should anything change, we will inform you before it does. Docs: Receiving Messages

Three things users do in a chat that used to arrive as unsupported now have a real shape. A post, reel or story mention shared on Instagram or Messenger is type: "share" with share_type, the link in share.url and the post caption in caption. A tap on any option you offered — a WhatsApp template quick-reply button, an interactive button or list row, an Instagram or Messenger quick reply or postback (Get Started, ice breakers, menu) — is an ordinary type: "text" whose text is the label the user saw, so one text handler covers typed answers and taps. And a reply to a specific message carries reply_to.message_id: the same id you already hold for the quoted message (your Fiwano UUID or the provider id you received), on every channel, for message.received and message.echo; an Instagram story reply carries reply_to.story. Messenger link previews no longer hide the message text, and WhatsApp unsupported_type now names the real content (edit, poll_creation, …). Docs: Receiving Messages

Stickers now arrive the same way on all three channels: as an ordinary image event, so an integration that already handles images receives them without extra code. On WhatsApp and Facebook Messenger the event is additionally marked with media.sticker: true, and Messenger stickers also carry Meta's persistent media.sticker_id; on Instagram a sticker is indistinguishable from a regular image. Stickers can be sent as well: media_type: "sticker" takes a WebP file for WhatsApp or a Meta catalog sticker_id for Messenger. The WhatsApp-only type: "sticker" value is no longer used; if your code tested for it, check media.sticker instead. Docs: Sending Messages

When Meta stops accepting Fiwano's access to a connected account (the app was removed in Meta Business settings, a required permission was revoked, or the Page or WhatsApp account became unavailable), the channel is now marked Needs reconnect in the portal and the account owner is emailed. Nothing is torn down: the channel stays connected, incoming and outgoing traffic is not blocked, and the mark clears by itself if access comes back on Meta's side. Reconnecting is the same connect flow for the same account and now works for an active channel too, keeping its channel_id, webhook settings and history. Docs: Channels

POST /api/v1/channels/setup-url now says exactly what is in the way. 402 means one thing only: the account has no active subscription. When subscriptions exist but every slot for that channel type is taken, the answer is 409 with detail.code no_free_slot and detail.occupied_by listing the channels holding the slots, so you know what to reconnect or release. The hosted setup flow also reports its outcome back to your redirect URI: slot_occupied when the user connected a different Meta account than the one holding your slot, access_denied when they cancelled, setup_failed for anything else. Docs: Errors

This page. New capabilities and meaningful improvements, newest first, with an Atom feed and a copy on GitHub.

status.fiwano.com: live component status, uptime history and an incident record kept in public git, so past events cannot be quietly rewritten.

Conversations that another app controls through Meta's handover protocol are handled explicitly: messages arriving while your channel is on standby are still delivered as message.received, and a send into such a conversation is rejected with an actionable hint instead of a generic Meta error. Docs: Errors

message.echo delivers a copy of messages your business sends outside Fiwano (WhatsApp Business app, Instagram inbox, Facebook Page inbox, Meta Business Suite, another integration), with optional delivered and read statuses for those echoes. Opt-in per channel. Docs: Event Types

A WhatsApp number, Instagram account or Page that is already connected in another Fiwano account is reported clearly at connect time, with a contact path, instead of failing silently.

Sends are paced per channel to stay within Meta's limits. When a channel or the platform is momentarily at capacity, the API answers with an explicit retry hint (429 or 503 with Retry-After) instead of a rejected Meta call. Docs: Sending Messages

Our high-availability setup was rebuilt with a 99.99% uptime target: faster, fully automatic recovery from component failures, with incoming messages preserved throughout.

Failure notifications to channel owners are consolidated into one digest email per channel, with the exact error and what to do about it, instead of one email per event.

Obviously invalid recipients are rejected before any Meta call, with a specific reason in the response. Docs: Sending Messages

The sender profile endpoint returns richer Messenger profiles (name and picture, when Meta provides them), with fallback sources when the primary lookup is unavailable. Docs: Sender Profile

WhatsApp template sends get the same Fiwano message ID and delivery status events as free-form messages. Docs: Templates

GET /subscriptions lists your plans and free channel slots, so an integration can check capacity before connecting a channel. Docs: Subscriptions

Connecting is more convenient and reliable when one Facebook user manages several Instagram accounts or Pages: choose the right one in Meta's dialog in a single login, and Fiwano resolves Meta's asset selection reliably even when accounts change over time. Docs: Channels

The Fiwano cookbook: a step-by-step integration playbook with the API reference alongside it, written for AI coding agents and people alike.

Documentation rebuilt as task-oriented pages with a Quickstart, an OpenAPI spec and an interactive API reference; also available as one Markdown file for AI agents. Docs

Instagram and Messenger connections moved to Meta's Facebook Login for Business: fewer steps, asset selection inside Meta's own dialog. Any channel can be reconnected in place: same channel ID, same webhook settings, same license. Docs: Channels

Media sends are validated before the Meta call (URL, type) and return specific errors instead of a generic Meta failure. Docs: Sending Messages

Localized pages for Brazil (pt-BR, including the documentation) and India, with reference pricing in BRL and INR.

n8n-nodes-fiwano is a verified n8n community node: WhatsApp, Instagram and Messenger in n8n workflows without code. Docs: n8n

Connect a WhatsApp number through Meta's official Embedded Signup flow in minutes: Cloud API, or Coexistence to keep using the WhatsApp Business app alongside the API. Docs: Channels

The inbound webhook path was rebuilt for higher throughput and lower relay latency from Meta to your endpoint.

Failed webhook deliveries and outbound sends are retried with backoff; the delivery status is reported once the outcome is known. Docs: Retry Policy

Choose which events each channel delivers (message.received, message.delivered, message.read and more). Nothing is delivered until you enable it. Docs: Event Types

Fiwano goes public: fiwano.com, self-service sign-up, licenses and billing. The v1 API contract is frozen from this point.

Third channel behind the same API: connect a Facebook Page, then receive and send Messenger messages with the same request and webhook formats.

Sent, delivered and read statuses arrive as webhook events.

Create, submit for approval and send WhatsApp templates from the portal and the API.

A few integrators we know start building on the API. First production traffic outside our own platform.

Fiwano becomes a Meta Tech Provider: businesses connect WhatsApp and Instagram through Fiwano's verified app, without their own Meta app or app review.

Built for our own client platform: WhatsApp and Instagram conversations behind one interface.