How to Connect Reepl to ViaSocket
Connect Reepl to ViaSocket to build automated content workflows without writing code.
ViaSocket connects Reepl to your other tools through automated flows. Use it to draft and schedule posts from elsewhere, or to route Reepl events into the systems your team already watches.
Before you start: you need a Reepl account on a Pro plan or above, and a Reepl API key. See API keys & scopes for how to create one.
Generate a Reepl API key
Open Settings → Developers
In Reepl, go to Settings → Developers, on the API keys tab.
Connect ViaSocket
Click Connect on the ViaSocket card. Its scopes come pre-ticked with what the integration actually uses: reading and writing drafts and posts, carousels, the AI tools, your profile, and webhooks:manage so triggers can register themselves.
Copy the key
Click Generate Key and copy it straight away — it is shown once and cannot be retrieved later.
Connect Reepl in ViaSocket
Create a flow
In ViaSocket, create a new flow.
Add Reepl as a step
Search for Reepl. If no native step is listed, use a generic HTTP step against https://api.reepl.io/v1, with your key in the X-API-Key header.
Authenticate
Paste the API key you generated in Reepl.
React to Reepl events
Add a webhook trigger in ViaSocket, then register its URL under Settings → Developers → Webhooks in Reepl and pick your events.
Every delivery is signed. Verify X-Reepl-Webhook-Signature before acting on a payload — the recipe is on the Webhooks page.
Troubleshooting
| Problem | Likely cause |
|---|---|
401 Unauthorized | The key is wrong, disabled, or was regenerated. Check Settings → Developers. |
403 Forbidden naming a scope | The key lacks that scope. Click Manage on the key in Settings → Developers and edit its permissions; the key value stays the same. |
403 with requiresUpgrade | The Reepl subscription is not active. Every endpoint except GET /external/me needs a paid plan. |
| A trigger never fires | Check the webhook subscription is still enabled — Reepl disables one automatically after 10 consecutive delivery failures. See Webhooks. |