FastBound Integration - Webhooks

Webhooks enable FastBound to push real-time event notifications to Orderwerks whenever something changes - a new acquisition is committed, a disposition is recorded, or a contact is updated. Instead of waiting for the next scheduled sync, webhooks ensure Orderwerks receives updates within seconds.

What Are Webhooks?

A webhook is a callback mechanism where FastBound sends an HTTP request to Orderwerks whenever a specific event occurs. This is a "push" model - FastBound tells Orderwerks about changes as they happen, rather than Orderwerks periodically "pulling" data through sync operations.

Benefits of Using Webhooks

Real-time updates - Changes in FastBound are reflected in Orderwerks within seconds
Reduced API calls - Less reliance on manual or scheduled sync operations
Immediate awareness - Know about new acquisitions, dispositions, and contact changes as they happen
Compliance support - Disposition and 4473 events are captured the moment they occur

Supported Webhook Events

Orderwerks can receive the following event types from FastBound:

Acquisition Events

Event	Description
Acquisition Created	A new acquisition is created in FastBound
Acquisition Committed	An acquisition is committed (finalized) in FastBound
Acquisition Deleted	An acquisition is removed from FastBound
Acquisition Transfer	An acquisition is transferred between accounts

Contact Events

Event	Description
Contact Created	A new contact (buyer, FFL, organization) is added
Contact Edited	An existing contact's information is updated
Contact Deleted	A contact is removed from FastBound

Disposition Events

Event	Description
Disposition Committed	A disposition is finalized in FastBound
Disposition Edited	An existing disposition's details are modified
Disposition Deleted	A disposition is removed from FastBound
Disposition Items Added	New items are added to an existing disposition
Disposition Items Edited	Items within a disposition are modified
Disposition Items Removed	Items are removed from a disposition

Form 4473 Events

Event	Description
4473 Completed	An ATF Form 4473 is completed for a transaction

Inventory Events

Event	Description
Location Changed	An item's physical location is updated in FastBound
Verification	An inventory verification event occurs

Item Events

Event	Description
Item Imported	A new item is imported into FastBound
Item Edited	An item's details are modified
Item Deleted	An item is removed from FastBound
Item Undeleted	A previously deleted item is restored
Item Undisposed	A previously disposed item's disposition is reversed

Other Events

Event	Description
Multiple Sale Report	A multiple sale report is filed

Setting Up Webhooks

Step 1: Get Your Webhook URL

Your Orderwerks webhook endpoint is configured automatically when you set up your FastBound account. Contact your Orderwerks administrator if you need the specific webhook URL for your account.

Step 2: Configure in FastBound

Log in to your FastBound account.
Navigate to your account's webhook settings.
Add a new webhook endpoint using your Orderwerks webhook URL.
Select the events you want to subscribe to (we recommend enabling all events for full integration coverage).
Save the webhook configuration.

Step 3: Set the Signing Secret

For security, webhooks use a signing secret to verify that incoming requests are genuinely from FastBound:

In FastBound, copy the Webhook Signing Secret generated for your webhook endpoint.
In Orderwerks, edit your FastBound account configuration.
Enter the signing secret in the appropriate field.
Save the account.

Important: The signing secret ensures that only legitimate webhook requests from FastBound are processed. Without it, webhook events may be rejected.

How Webhook Events Flow into Orderwerks

When FastBound sends a webhook event:

Orderwerks receives the event at the configured endpoint.
The signing secret is verified to confirm the event is authentic.
The event is processed based on its type:
- Acquisition events trigger serial import/update operations
- Contact events update contact records
- Disposition events update order disposition data
- Item events update serial metadata
The data is updated in Orderwerks in real time.

If processing fails, the error is captured in the Error Log for review and retry.

Webhooks vs. Manual Sync

Feature	Webhooks	Manual Sync
Speed	Real-time (seconds)	On-demand or scheduled
Coverage	Individual events as they happen	Full batch of all changes since last sync
Use Case	Day-to-day operations	Initial setup, catching up after downtime, reconciliation
Reliability	Depends on network/webhook delivery	Reliable batch processing

Best Practice: Use webhooks for real-time updates during normal operations, and manual sync as a backup for initial data loads or when catching up after an outage.