Skip to content
English
  • There are no suggestions because the search field is empty.

Getting Started with Incoming Webhooks

This guide explains how to configure Incoming Webhooks to push data from external ticketing, e-commerce, or marketing platforms (e.g., Shopify) directly into Tradable Bits.

Overview

Incoming webhooks allow third-party applications to push fan data, orders, and tickets into Tradable Bits in real time via HTTP POST requests:

  • Automated Data Ingestion: Automatically create or update fan records whenever a purchase or sign-up occurs on an external site.
  • Custom Field Mapping: Explicitly map fields from external incoming JSON payloads to target fields in Tradable Bits.

Primary Identifier Requirement: Every incoming payload must contain either an email or a phone field mapped to a fan record to create or update an entry. Unmapped payload fields are automatically ignored.

Setup

Generate an Incoming Webhook Connection

Under Ticketing or Email Platform:

  • Select your Network (e.g., Shopify).
  • Select an API Key from the dropdown menu.
  • Enter a Data Source Name to identify where the data is coming from (e.g., Main Store Checkout).

Click Generate on the right side of the row to create your unique webhook URL.

Copy and paste this generated URL into your external ticketing or e-commerce platform's webhook settings.

Configure Incoming Fan Field Mapping

To ensure data lands in the correct CRM fields, map your incoming JSON payload keys to target fields in Tradable Bits under Incoming Fan Webhook Configuration:

  1. Enter the incoming key name from your source platform in the Source Key column (e.g., user_email).
  2. Select the corresponding Tradable Bits field in the Target Field (crm_fans) dropdown (e.g., email).
  3. Click + Add Mapping to add additional row mappings 
  4. Click Save.

Note: Only mapped fields are ingested into the CRM. Any unmapped key-value pairs present in the incoming payload will be safely ignored.

Expected Payload Schema

The expanded Expected Payload accordion displays the standard JSON structure accepted by the incoming endpoint:

Ex.

⚠️ Important

Webhook notifications are delivered in real time as single events. In the event of a service disruption (whether on the Tradable Bits platform or your receiving server), undelivered data will not be automatically re-sent. Webhooks attempt delivery only once.

Still need assistance? Please reach out to your Customer Success Team or contact support@tradablebits.com