Documentation menu

EventSend Documentation

Send an event with one HTTP request and route it to Slack, Discord, Telegram, your phone, or your own webhook — no SDK required.

EventSend is a notification router. Your app — plus the tools you already use, like Stripe — sends events to one endpoint, and EventSend routes them by rule to Slack, Discord, Telegram, your own phone, or your own webhook, with retries, signatures, idempotency, and a per-attempt delivery log.

There is no SDK to install. Sending an event is one HTTP POST:

curl -X POST https://eventsend.io/api/events \

  -H "Authorization: Bearer es_YOUR_TOKEN" \

  -H "Content-Type: application/json" \

  -d '{

    "event": "user-signup",

    "message": "New user signed up: [email protected]",

    "level": "success",

    "payload": {"user_id": 123, "plan": "free"}

  }'

Start here

  • Quickstart — your first delivered event in 60 seconds, with copy-paste snippets for curl, JavaScript, Python, Elixir, and Go.
  • Concepts — how routes, topics, destinations, sources, and connections fit together, and how routing rules decide what gets delivered.

Using an AI coding tool?

You do not have to write the integration yourself. There is a one-page prompt that asks your coding agent to read your codebase, list the moments worth knowing about in your product, write a small server-side helper, and instrument the success and failure paths — with a note about where a secret lives in that stack. Pick your tool: Cursor, Claude Code, Codex, Devin Desktop, GitHub Copilot, Lovable, Bolt, v0 or Replit.

Ask your AI about your events

Once events are flowing, the same assistant can read them back. EventSend has a read-only MCP server: connect Claude Code, Cursor, Claude Desktop, claude.ai or ChatGPT to https://eventsend.io/mcp and ask in plain language — "did anything fail in checkout today?", "what did customer cus_9Xk2 do before cancelling?", "are deliveries to Slack failing?". It is on every plan, Free included, and nothing it does can change your account.

Reference

  • Events API — every field, limit, and response code for POST /api/events.
  • Webhook signatures — verify that a webhook delivery really came from EventSend, with snippets in Node.js, Python, and Elixir.
  • Delivery and retries — the retry schedule, circuit breakers, and what each delivery status means.
  • MCP server — the endpoint, both credentials, client setup, and the nine read-only tools an assistant can call.

Connect a source

  • Stripe — turn Stripe webhooks into events without writing any code.

Recipes