Changelog

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.