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

# Enabling Webhook Notifications

> Instructions for turning on and configuring webhook notifications in SimpleTix.

## 1. Enable Webhooks

* Log in to your SimpleTix Manager account. You can either go directly to the [Advanced Options page](https://manager.simpletix.com/general/advanced-options) or log in at [https://manager.simpletix.com/](https://manager.simpletix.com/) and click on **Settings** in the top rail.
* In the **Settings** menu, select **Advanced Options** from the left-hand side.
* Locate the webhook options section where you can configure both types of webhooks.

## 2. Configure Your Webhook URLs

* For Order Webhooks: Toggle on "Turn on the Post Order webhook feature" and enter your order notification endpoint URL.
* For Post-Scan Webhooks: Toggle on "Turn on the Post Scan webhook feature" and enter your scan notification endpoint URL.
* Each webhook URL is the endpoint on your server where SimpleTix will send POST notifications.
* Provide URLs that are capable of accepting incoming POST requests. These endpoints should be secure (using **HTTPS**) and able to process URL-encoded form data.

## 3. Webhook Types and Trigger Details

SimpleTix offers two types of webhooks that can be configured from the Advanced Options section:

### Order Webhook

* When a new order is created via SimpleTix, a POST request is sent to your configured URL.
* This webhook triggers immediately after an order is successfully completed.

### Sample Order Webhook Response

The Order webhook sends data in a form-encoded format (maintained for legacy and backwards compatibility):

```
Address=&City=Boston&Country=US&DiscountTotal=0.00&Email=john.doe%40example.com&FirstName=John&Identifier=aa123456-1a2b-3c4d-5e6f-7890abcdef12&ApplicationId=123a4b56-c789-0d1e-2f3g-456h7i8j9k0l&LastName=Doe&OrderDate=5%2f5%2f2025+3%3a25%3a12+PM&OrderNumber=I-1234567A-0&OrderStatus=Order+Complete&Organization=&Phone=5555551234&PostalCode=02101&OrderTotal=0.00&ServiceFeeTotal=0.00&SubTotalAmount=0.00&TaxTotal=0.00&TransactionType=Free
```

<Info>
  Note the difference in formats: Order webhooks use the legacy form-encoded data format for backwards compatibility, while the newer Post-Scan webhooks use JSON. Your endpoint will need to handle the appropriate format for each webhook type.
</Info>

### Post-Scan Webhook (New Feature)

* Sends a POST request when a ticket is scanned using the SimpleTix Organizer app.
* This webhook triggers only for actual scans and will not fire when attendees are admitted manually through the web interface.
* Enables real-time tracking and custom actions when attendees check in at your event.

<Info>
  Both webhook types can be configured independently from the Advanced Options page, allowing you to send different types of notifications to different endpoints as needed.
</Info>

### Sample Post-Scan Webhook Response

When a ticket is scanned, you'll receive a response like this:

```json theme={null}
{
  "Barcode": "123456789012345",
  "Code": "Success",
  "Result": {
    "ParticipantId": 1234567,
    "ParticipantFirstName": "John",
    "ParticipantLastName": "Doe",
    "EventType": 0,
    "SectionTitle": "VIP Access",
    "IsPaid": true,
    "CheckIdAtDoor": false,
    "CheckedIn": "0001-01-01T00:00:00"
  },
  "Message": "Event Name Section: VIP Access",
  "WebhookUrl": "https://your-webhook-endpoint.com/scan-notifications/"
}
```

This response includes the participant details, ticket information, and scan result, allowing you to trigger custom actions in your systems when attendees arrive at your event.

<CardGroup cols={2}>
  <Card title="Extended Notification Configuration" icon="square-1" href="/docs/advanced-options/set-up-bcc-notifications-for-ticket-sales">
    Guidance on configuring BCC notifications for ticket sales.
  </Card>

  <Card title="Connect to Zapier" icon="square-2" href="/docs/integrations/connect-simpletix-to-zapier/">
    Connecting to Zapier for more automation.
  </Card>
</CardGroup>