REST API

Build on ForgeSend. Rate-limited and scoped by design.

Per-workspace rate limiting, a dedicated Sending API guard, and an outbound webhook dispatcher with automatic retry — all managed from Settings, no code required to configure.

Start free trial →See pricing →
Webhook deliveryDelivered
event →campaign.reply.received
signature →sha256=4f2a…
Retry policy3 attempts, backoff
01

Per-workspace rate limiting

The Contacts, Lists, Campaigns, Analytics, and Sending APIs are all protected by rate limiting scoped to each workspace, so one workspace's usage can never crowd out another's.

02

A dedicated Sending API guard

Sending requires its own dedicated sending-scoped API key — workspace- and inbox-scoped — on top of standard authentication. A key built for reading analytics can't be used to send a message.

03

Outbound webhooks, HMAC-signed

Six event types dispatch as HMAC-signed payloads, so a receiving endpoint can verify a webhook genuinely came from ForgeSend. Failed deliveries retry automatically with backoff.

04

Managed entirely from Settings

Register an endpoint, view delivery history, enable, disable, or delete a webhook — all from the Settings UI. No code required to configure any of it.

The same scoped API keys also power ForgeSend's MCP server and the n8n integration node, so any automation you build with one authentication model carries over to the others.

Frequently asked questions

What does the Sending API guard actually check?
Sending requests must present a dedicated sending-scoped API key that's also workspace- and inbox-scoped, on top of ForgeSend's standard authentication — a key without the sending scope can't trigger a send.
How many webhook event types are there?
Six event types are currently supported. Each delivery is HMAC-signed so your endpoint can verify it genuinely came from ForgeSend.
What happens if a webhook delivery fails?
Failed deliveries are retried automatically with backoff. Delivery history — including failures — is visible from the webhooks tab in Settings.
Do I need to write code to set up a webhook?
No. Registering an endpoint, viewing delivery history, and enabling, disabling, or deleting a webhook are all done from the Settings UI directly.

Related features

n8n Integration
A ForgeSend node for n8n, built on the same scoped API keys.
MCP Server
Connect any MCP-compatible AI agent to manage campaigns, leads, and analytics.
Pre-Send Guardrails
Block campaign launch until DNS, warmup, and list checks pass.

Rate-limited. Scoped. Ready to build on.

Generate a scoped API key from Settings and start building — rate limits and guardrails come standard.

Start free trial →Explore all features →