---
title: "AgendaForge Webhooks: Signed Event JSON"
description: "AgendaForge sends 16 HMAC-signed webhook event types as JSON the instant your event data changes. Subscribe via the public REST API and verify every delivery."
canonical: "https://agendaforge.app/integrates-with/webhooks"
last-updated: 2026-07-01
---
# AgendaForge Webhooks: Signed Event JSON
> AgendaForge sends 16 HMAC-signed webhook event types as JSON the instant your event data changes. Subscribe via the public REST API and verify every delivery.
Canonical page: https://agendaforge.app/integrates-with/webhooks
Last reviewed or updated: 2026-07-01
Content type: integration

AgendaForge webhooks push HMAC-signed JSON to an endpoint you control the instant something changes in your event: a contact is added, a sponsor moves, a session is edited, a speaker confirms. Instead of polling the dashboard or scraping an export on a timer, your own systems react in real time. You manage everything through the public REST API at /api/v1 with an API key that begins afk_live_: subscribe an endpoint, unsubscribe it, GET a trigger sample to see the exact payload before you write a line of handler code, and even POST to create a contact when you want to push data back in. There are 16 HMAC-signed webhook event types, every delivery is signed so you can prove it came from us, and it is genuinely shipped, not a roadmap promise. This is the escape hatch that connects AgendaForge to whatever you run, from a homegrown database to a Zapier or Make scenario, all of it through the same REST API rather than a one-click connector.

Official integration website: /docs/api

## What it does

- Delivers HMAC-signed JSON to your endpoint the moment an event record changes: contacts, sponsors, sessions, speakers, submissions, reviews, and event lifecycle.
- Lets you subscribe and unsubscribe endpoints programmatically through the public REST API at /api/v1 using an afk_live_ API key.
- Exposes GET trigger samples so you can inspect the exact payload shape for any event type before you build your receiver.
- Doubles as an inbound door: the same API key can POST to create a contact, so the integration both listens and writes back.
- Connects AgendaForge to anything that can receive an HTTPS POST (your own services, a queue, or a Zapier/Make scenario) over the REST API, with no native connector required.

## Trigger and result

| Event | Result |
|---|---|
| contact.* (added / updated / removed) | Fires when a contact (speaker, sponsor contact, attendee) is created, edited, or removed, so your CRM or mailing list stays current automatically. |
| sponsor.* (added / updated / removed) | Fires when a sponsor is created, edited, or removed, a clean hook for keeping an external CRM or billing system in step without a manual export. |
| session.* (added / updated / removed) | Fires when a session changes: the usual trigger for keeping an external site, app, or schedule cache in sync with your agenda. |
| speaker, submission, review, and event lifecycle events | Fires on speaker confirmed and declined, submission created and status changed, review completed, and event published: the rest of the 16 signed types. |

## Setup

1. **Stand up an endpoint and subscribe.** Point a publicly reachable HTTPS URL at your handler, then POST to /api/v1 with your afk_live_ API key to subscribe it to the event types you care about. Pull a GET trigger sample first to see the exact payload before you write the handler.
2. **Verify the HMAC signature on every delivery.** Each delivery is HMAC-signed. In your handler, recompute the signature over the raw request body and compare it to the one we send before you trust the payload. That is how you confirm the request really came from AgendaForge and not a spoofer.
3. **React, and optionally write back.** Process the JSON however you like: sync a database, queue a job, fan out to other apps. The same API key also lets you POST to create a contact, so the integration can both listen for changes and push new records into AgendaForge.

## Worth knowing

Webhook subscriptions are org-level, not per-event: an endpoint receives matching events across your whole organization, so filter by event in your own handler if you only care about one. You also have to operate the receiving end: a reachable HTTPS endpoint, and signature verification on every delivery. Unlike our Slack and ClickUp connectors, this is a developer integration, not a point-and-click per-event setup in the dashboard.
## Frequently asked questions

### How do I subscribe and unsubscribe an endpoint?

Through the public REST API at /api/v1, using an API key that begins afk_live_. You POST to subscribe an endpoint to the event types you want and call the API again to unsubscribe. It is programmatic, so you can manage subscriptions from your own code or deploy scripts rather than clicking through a dashboard.

### How do I verify a webhook delivery is genuine?

Every delivery is HMAC-signed. In your handler, recompute the HMAC over the raw request body using your endpoint's signing secret (shown once, when you add the webhook in AgendaForge) and compare it to the signature we send. Only trust the payload when they match. This protects you from spoofed or replayed requests, and it is the one step you should never skip when building a receiver.

### Are webhooks scoped per event or per organization?

Subscriptions are org-level, not per-event. An endpoint receives matching events across your whole organization, so if you only care about one event, inspect the payload and filter by event in your own handler. This differs from our native Slack and ClickUp connectors, which are configured per event in the dashboard.

### Can I push data into AgendaForge, or only receive it?

Both. The same afk_live_ API key that manages webhook subscriptions also lets you write in: you can POST to the REST API to create a contact, and GET trigger samples to inspect payload shapes. So one key covers listening for outbound events and pushing records inbound. The full reference lives at /docs/api.

---

AgendaForge is an AI-native event-management platform. Public machine-readable index: https://agendaforge.app/api/ai