Nautilus Flow API documentation: authentication, webhooks, messaging, the 24-hour customer service window, public ecommerce order events, and integration guides.
Nautilus Flow’s public API lets a store, CRM, or script send WhatsApp Cloud API messages and receive events. Create a key under Settings, then Integrations and API. The interactive reference on this page has request shapes. This section is the part an answer engine should quote.
Generate a key in the dashboard. Send it on every request as X-API-Key or Authorization: Bearer. If both headers are present, X-API-Key wins. A missing, invalid, or expired key returns 401. Rotating a key revokes the old one and shows the new raw key once.
X-API-Key
Authorization: Bearer
The base path is /api/v1 on your API host. Public integrator routes live under /api/v1/public/.
/api/v1
/api/v1/public/
You can send a template or, when the customer’s 24-hour window is open, a free-form message. Outside that window Meta only accepts an approved template. Nautilus Flow rejects free-form sends when the window is closed so the number is not burned on a delivery Meta would refuse. Sending a template does not reopen the window. The customer has to message again.
Template names must already be approved in the workspace. Marketing templates still require a recorded opt-in. Utility templates, such as order shipped, still require you to attest that you have permission for that transactional message.
Outbound webhooks notify your server of inbound messages and status updates. Register the HTTPS callback in the workspace, verify the signature, and answer quickly. Inbound Meta webhooks are configured on the Nautilus deployment, not pasted into this public page. Failed deliveries can be inspected in the product’s webhook failure log.
A customer message, including a Click-to-WhatsApp ad tap, opens a 24-hour customer service window on Cloud API. Inside it, session messages are allowed. After it, only templates. This is Meta’s rule. The WhatsApp Business mobile app does not open or extend that Cloud API window.
Read the longer guide on the 24-hour window and the opt-in and STOP rules before you automate a broadcast.
Shopify and WooCommerce, or any client of the public order-event API, can submit order placed, fulfilled, cancelled, and abandoned checkout. Map each event to a Meta-approved template. Abandoned checkout should be a utility template about that checkout, and the send should cancel when the order is placed.