The recipes below are complete workflows built from the public Furcata API. Each one shows the calls in order, the fields that matter, and the mistakes that are easy to make.
All three recipes are built from the same small set of capabilities.
- Contacts — the people you message, identified by phone number.
- Messages — a single send to between one and fifty recipients.
- Webhooks — how Furcata tells your system what happened.
- Reports — what was sent, and what it cost.
One message, many recipients
A single send accepts up to fifty recipients. For larger audiences, send in batches rather than one enormous request, and give each batch a distinct idempotency key so a retry cannot double up.
Any send can be retried by your own code or by your network. An idempotency key ties a retry to the original request so the recipient gets one message, not two. Generate the key from something stable about the send — an order id, an appointment id, a batch number — not from the current time.
A send only tells you that Furcata accepted the message. Delivery outcomes arrive by webhook. Subscribe to delivery and failure events and treat those as the source of truth for whether a message arrived.
A contact who has opted out is not messaged, whatever your workflow asks for. Build your process assuming that some fraction of every list will be skipped, and do not treat a skip as an error.
Pick a recipe and build it
Each recipe is self-contained. Start with appointment reminders — it exercises contacts, sends, idempotency and webhooks in one small flow.
Start with appointment reminders