Pipe URLs into Storyflo. Anywhere.

Endpoint

Public, IP-rate-limited, no API key. Returns 202 Accepted with a short JSON acknowledgement.

POST https://api.storyflo.com/v1/intake/web
Content-Type: application/json

{ "url": "https://example.com/article-to-narrate" }

Zapier

1. In Zapier, click Create Zap → pick a trigger app (e.g. RSS by Zapier, Gmail, Twitter, Notion).
2. Configure the trigger so the output includes the URL you want narrated (e.g. an RSS item's link, an email's first link, a tweet's URL).
3. Add an action: Webhooks by Zapier → POST.
4. Set the URL to https://api.storyflo.com/v1/intake/web.
5. Payload Type: JSON. Data: add a single field url with the value mapped from your trigger.
6. Test → Publish. Zaps fire automatically thereafter.

URL          https://api.storyflo.com/v1/intake/web
Method       POST
Data
  url        {{trigger__link}}    ← Zapier field-mapping syntax
Headers
  Content-Type   application/json

IFTTT

1. In IFTTT, create an Applet → pick a trigger (RSS Feed, Gmail, Notion, etc.).
2. For the action, choose Webhooks → Make a web request.
3. Set URL to https://api.storyflo.com/v1/intake/web.
4. Method: POST. Content Type: application/json.
5. Body: {"url": "{{EntryUrl}}"} — replace EntryUrl with the field name your trigger exposes (RSS uses EntryUrl; Gmail usesBodyPlain etc.).
6. Save the Applet. New trigger events fire automatically.

Smoke test from your shell

curl -sS -X POST 'https://api.storyflo.com/v1/intake/web' \
  -H 'Content-Type: application/json' \
  -d '{"url": "https://www.bbc.com/news/articles/c80jl4j8gx5o"}'

On success you'll see a 202 Accepted with a JSON ack including the new article slug. The render worker picks it up within a few seconds; check /listen/queue (or the public feed) shortly after.