> ## Documentation Index
> Fetch the complete documentation index at: https://developer.swoogo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> HTTP callbacks that fire when resources are created, updated, or deleted

Swoogo can send HTTP callbacks (webhooks) when resources are created, updated, or deleted. Configure webhooks via the API or the Swoogo UI to keep external systems in sync with your event data.

## What you can do

* **Create and manage webhooks** with target URLs and trigger conditions
* **Organize webhooks into groups** for easier management
* **Configure payload format** — JSON or form-encoded
* **Set custom headers** for authentication with your receiving endpoint

## Supported trigger objects

Webhooks can fire on changes to these resources:

* `event`
* `contact`
* `registrant`
* `speaker`
* `sponsor`
* `session`
* `session_attendance`
* `registrant_line_item`

## Related resources

| Resource           | Relationship                           |
| ------------------ | -------------------------------------- |
| **Webhook Groups** | Organizational containers for webhooks |

## Key concepts

**Webhook groups** — Group related webhooks together for easier management. A webhook group contains one or more webhooks that share common organizational context.

**Payload formats** — Webhooks can deliver payloads as `json` (application/json) or `post` (form-encoded). Choose the format that best fits your receiving endpoint.

**Retry logic** — When a webhook delivery fails, Swoogo will retry the request. Configure your receiving endpoint to return a `2xx` status code to acknowledge receipt.