Developer & support

Four tabs, all genuinely functional today: API key generation, webhook endpoint management, a real two-way support ticket system, and a shared feature request board.

On this page

API Webhooks Support Feature Requests Where to go next

API

The API tab is where you generate API keys — the credential ForgeSend's MCP server (and any other external tool you authorize) uses to act on your workspace without a browser login.

API Keys — read only

API Keys

Generate keys for external tools — like the MCP server — to access this workspace without a browser login. Each key is shown in full only once; it can never be displayed or recovered afterward.

Key label (e.g. MCP server)

Generate key

Generating a key requires being a workspace owner — everyone else sees "Only the workspace owner can generate or revoke API keys" instead of the form. Right after you generate one, it's shown exactly once in a full-value copy box with a "Copy this key now — it will not be shown again" warning and a Done, I've saved it button to dismiss it; only the key's prefix is ever displayed again.

Give the key a descriptive label like "MCP server" when you create it — the label is the only self-chosen thing shown in the keys table afterward, so it's how you'll tell keys apart later.

Active keys — read only

LabelKeyCreatedLast used

MCP serverfs_live_7f2a…Jul 2, 2026Jul 16, 2026

With no keys yet, the table is replaced with "No API keys yet — Generate one above to get started." An owner can revoke any key from this table with one inline confirmation (Sure? → Yes); revoking takes effect immediately — a revoked key is rejected on its very next use, with no grace period.

This same key authenticates two things: ForgeSend's MCP server — an AI agent uses it as a bearer token to call campaign, contact, and read-only analytics tools against your workspace — and direct calls to ForgeSend's REST API. See MCP server — Generating an API key for the MCP connection flow and full tool list.

Scope a key to only the resources an integration actually needs — each resource has independent read and write permissions:

Scopes — read only

Permissions

contacts:readcontacts:writecampaigns:readcampaigns:writeanalytics:readanalytics:writelists:readlists:writesending:readsending:writewebhooks:readwebhooks:write

API requests are rate-limited per workspace, independent of any other workspace's traffic — going over the limit returns an HTTP 429 until the window resets.

Webhooks

The Webhooks tab registers HTTP endpoints that ForgeSend calls in real time when workspace events happen, instead of you having to poll the API for changes.

Webhooks — read only

Add endpoint

https://yourapp.com/webhooks/forgesend

Add endpoint

RepliedBouncedSend failedUnsubscribedOpenedClicked

Registered endpoints — read only

EndpointEventsStatusLast delivery

yourapp.com/webhooks/forgesendReplied, BouncedEnabled2 min ago

Each endpoint subscribes to one or more event types — Replied, Bounced, Send failed, Unsubscribed, Opened, and Clicked — and every delivery is signed, so you can verify a payload actually came from ForgeSend before trusting it. An endpoint can be disabled without losing its configuration, or removed outright.

Opened and Clicked are selectable event types today, but neither fires yet — email open and link-click tracking isn't wired into the webhook dispatcher yet. Deliveries currently only go out for Replied, Bounced, Send failed, and Unsubscribed.

Support

A ticketing system: a list of your tickets, a new-ticket form, and a reply thread per ticket.

Support Tickets — read only

Support Tickets

New ticket

Reply thread stopped matching after client renamed subject

In Progress

Bug · #a1b2c3d4 · 2 replies

A new ticket needs a Subject, a Category (Bug, Billing, Account, Deliverability, or Other), and a Description — no file attachments. Submitting shows "Ticket submitted — we'll respond within 24 hours" and opens straight into the ticket's thread. Status is one of Open (green), In Progress (amber), or Resolved (gray). Replying is a real, two-way thread — your replies show as "You", ForgeSend's as "ForgeSend Support" — and replying to a resolved ticket automatically reopens it.

Feature Requests

A shared board where anyone in a workspace can submit ideas and upvote others'.

Feature Requests — read only

AllPlannedShipped

▲18

Per-variant reply-rate breakdown in Analytics

Planned

A new request needs a Title, a Category (UI, API, Integrations, Deliverability, Enrichment, or Other), and a Description. Submitting it auto-upvotes it for your workspace — upvoting is one vote per workspace, not per person. The list sorts by upvote count first, then most-recent as a tiebreaker. Status is one of Submitted, Under Review, Planned, In Progress, Shipped, or Declined; a status change can come with a short note from ForgeSend, shown inline once a request is Planned or further along.

Where to go next

Next: Warmup overview