> For the complete documentation index, see [llms.txt](https://help.tacinsight.com/fast-weigh-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tacinsight.com/fast-weigh-knowledge-base/references/ticketing-app/setup/ticketing-app-webhooks.md).

# Ticketing App Webhooks

{% hint style="warning" %}
Ticketing App Webhook Events must first be enabled in the Server Settings under "Beta Features"
{% endhint %}

## Overview

Fastweigh supports custom payloads that are triggered based on specified ticketing app events. 

The payload expects JSON formatting and will automatically append the header:

`Content-Type: application/json`

<figure><img src="/files/JISoDtz0sIUkAMjYnU15" alt=""><figcaption></figcaption></figure>

**Description:** Display name for internal reference only.

**Priority:** 1 is the Highest, 100 is the lowest. Webhook events with the highest priority will run first.

**Method:** Supports POST, PUT, DELETE and GET

**Endpoint URL:** External Webhook URL should be entered here.

**Event to Trigger:** Select the Fastweigh Server Event to trigger the Webhook Event.&#x20;

**Filter Event to Lane:** Optionally, events can be filter to a specific lane, if your installation has multiple.

**Headers:** Additional Headers can be configured, such as an API Key. `Content-Type: application/json` will be appended automatically.

**Payload:** Static JSON payload. It is not currently possible to reference fields from events (Such as Ticket Number or Current Scale Weight)

## Testing Webhooks

We recommend using [Webhook.site](https://webhook.site/?utm_source=chatgpt.com) to validate webhook functionality during setup and troubleshooting.

Webhook.site automatically generates a unique testing endpoint that can receive and display webhook payloads in real time. This allows you to verify that requests are being sent successfully and to inspect the contents of each payload.

#### Using Webhook.site

1. Navigate to Webhook.site.
2. A unique endpoint URL will be generated automatically. If you have visited the site recently, your previous endpoint may still be active.
3. Click **Edit** and Enable "Add CORS Headers" (Top Right)
4. Click **Copy** and select **URL** to copy the generated endpoint.
5. Paste the copied URL into the **Endpoint URL** field of your webhook configuration.
6. Trigger the webhook and monitor Webhook.site to view the incoming requests and payload data.

#### Payload Requirements

Webhook.site can receive any valid JSON payload. While the site provides example payloads for testing, you may send any JSON-formatted data that meets your application's requirements.

Using Webhook.site is an effective way to confirm webhook connectivity, validate payload structure, and troubleshoot integration issues before connecting to a production endpoint.

<figure><img src="/files/q37wcNRE0hGYzTyD01tq" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/qQDsjTObTcV776jkUJFj" alt=""><figcaption></figcaption></figure>

If using the payload example:

```json
{
  "key": "hello",
  "world": 0,
}
```

Fastweigh Configuration should look like:

<figure><img src="/files/u9SKmUVMxd2plwU94Gvk" alt=""><figcaption></figcaption></figure>

Manually triggering an event by clicking "Test Event" will send a payload to the webhook.site service:

<figure><img src="/files/3vdJtfIpXSKRezbShKTX" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.tacinsight.com/fast-weigh-knowledge-base/references/ticketing-app/setup/ticketing-app-webhooks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.