Developers Platform - Tradable Bits API, SDK, CSS Library & Integrations

Fan Marketing Awards 2025 The best of fan marketing from the past year

Developers

Our platform was built to be flexible and intuitive for developers like you. You own all the data you collect with Tradable Bits. Our API and SDK are designed to make it easy to access your fan data, tickets and campaigns at any time, on your terms Customize the front end of any of your campaigns with the help of our documentation, complete with examples. Our RESTful API helps you access, send or receive fan data from our system to your endpoints quickly and securely. Enrich your Fan CRM and Tickets Analytics with data from other CRM systems through our many integrations. Have any questions about our developers platform? Our support team is happy to help.

Tradable Bits Server API

NEVER EXPOSE API SECRET IN NON SECURE ENVIRONMENT E.G. BROWSER OR MOBILE APP. THIS KEY MUST BE KEPT SECURE ON YOUR SERVER SIDE.

Most of CRM Data can be accessed with our HTTP based API. Calls should be sent as application/x-www-form-urlencoded and will return JSON data. Authentication is handled using API Keys. The system recognises two form of keys: Public and Secret. Public is meant to be shared and can be used in insecure environments whereas Secret key is reserved for server-to-server communications and must be kept private. Api keys can be sent either in the request body as api_key and api_secret or as headers using Api-Key and Api-Secret. You can manage key under profile section once you log into Tradable Bits.

There is a limit to how often you can call Tradable Bits. Currently, it's set to 600 calls per minute. If you need a higher limit, please reach out to us.

This Call Requires api_secret as additional parameter

Calls with Lock icon are meant for data exchange or called from the server side. Each call must include api_secret as either GET or POST parameter

This Call Requires api_key as additional parameter

Calls with UnLock icon are meant to be integrated into mobile or web applications and require api_key as additional parameter for all requests

Introduction

Console

Segments

GET /v1/segments GET /v1/segments/<segment_type>/<segment_id>/status GET /v1/segments/<segment_type>/<segment_id>

Crm

Ent

Streams

GET /v1/streams GET /v1/streams/<stream_key>/records POST /v1/streams/<stream_key>/records GET /v1/streams/<stream_key> GET /v1/streams/<stream_key>/<feed_record_id> POST /v1/streams/<stream_key>/<feed_record_id>

Sessions

POST /v1/sessions/wifi_fans GET /v1/sessions/check POST /v1/sessions/signup POST /v1/sessions/connect GET /v1/sessions/<session_uid> GET /v1/sessions/<session_uid>/fan POST /v1/sessions/<session_uid>/fan GET /v1/sessions/<session_uid>/points

Idols

POST /v1/idols GET /v1/idols GET /v1/idols/<idol_uid> GET /v1/idols/events

Reports

GET /v1/reports GET /v1/reports/<report_uid>

Ads

POST /v1/ads/projects/<project_uid>/budget_lines

Misc

GET /v1/trackers GET /v1/trackers/<tracker_id> POST /v1/trackers GET /v1/trackers/events GET /v1/props/<prop_name> GET /v1/geoip GET /v1/shp_lookup POST /v1/yinzcam_subscription GET /v1/account_ad_stats GET /v1/account_ad_stats_by_campaign GET /v1/template_portals GET /v1/template_portals/<portal_uid> POST /v1/template_portals POST /v1/template_portals/<portal_uid> DELETE /v1/template_portals/<portal_uid>

Apps

Informational

GET /v1/networks

API Console

API Access allows you to query Stream and user data using RESTful API, as well as register for push notification from our CRM system. API Reference is broken into sections by topic: Meta Apps (Campaigns) Data, Stream Data, CRM Data.

Each Request must include api_key as parameter. You can generate an API key in the Manage Centre.
You may try most of our API calls here. Your API Key will be automatically appended if available.

Input

https://tradablebits.com/api/v1/

Request Type

API Keys ( usually only one of Key or secret is required)

API KEY

API Secret

Additional Arguments

Add Argument

Results

Generated URL

segment_type	tag/filter/snapshot
segment_id	If on the segment. ID is unique with in corresponding segment type
segment_name	Character descriptor for the segment

fan_count
email_count
phone_count
phone_subscribe_count
email_subscribe_count
last_update_timestamp	Update for the last update of the fan

search_uid	Has to be supplied to get additional records. Currently result set may be limited and will return search_uid if paging is required
limit	Max size of the page. Values from 0 to 10000 are supported. If skipped, 1000 will be used

fan_id	Primary key for the fan
email
phone
first_name
last_name
is_subscribed	Boolean flag on whether there is explicit opt-in into email comm
is_phone_subscribed	Boolean flag on whether there is explicit opt-in into SMS comm

campaign_title	Name of custom campaign
property_name	Name of the property to track

API Console

Segments Calls

Crm Calls

Ent Calls

Streams Calls

Sessions Calls

Idols Calls

Reports Calls

Ads Calls

Misc Calls

Apps Calls

Informational Calls

account_id
title
page_tab_id
stream_key
app_type
is_active
creation_timestamp
winner_fan_id

min_activity_id	Window Specifier. Will return only activities with activity_id greater than given
max_activity_id	Window Specifier. Will return only activities with activity_id less than given
limit	Optional parameter to specify max row count. Max. allowed value is 500
page_tab_id	Optional Filter to participants of specific campaign
activity_date	Optional Filter to participants for specific date
include_details	Boolean flag to include additional details: fan, idols, connections. Default = False

activity_id	Unique Identifier for the activity
account_id	Tradable Bits Account ID
fan_id	Unique Identifier for the fan record
creation_date	ISO Date of activity
campaign_title	Title of the campaign
app_type	For contests - type of contest
page_tab_id	Contest ID reference (set for contests only)
opted_in_business_ids	Opted in business ids of the fan
is_subscribed	Opted in to Email Marketing
is_phone_subscribed	Opted in to SMS Marketing
creation_timestamp	ISO timestamp of activity
page_tab_id	Campaign ID reference
stream_key	If activity is tied to stream - reference for stream
ip_address	IP Address
user_key	Facebook/Spotify/etc User Key
name	Full Name
email	Email
details	JSON structure of campaign details (varies by campaign)
fan	Fan Structure as per documentation
networks	List of connected networks
idol_names	List of connected Idols

first_name
last_name
email *
phone
campaign_title
province
postal_code
country_code
is_subscribed
is_phone_subscribed

show_hidden	Show fans who are hidden from the public leaderboard in the campaign. Default = False
limit	Limit the number of fans fetched from the leaderboard. Default = 10

rank	Leaderboard rank
fan_id	Unique Identifier for the fan record
display_name
is_hidden	If the fan is hidden from the public leaderboard in the campaign (If applicable)
activity_timestamp	Timestamp of when the fan completed the activity (If applicable)
points	Number of points gained in the campaign (If applicable)
balance	Balance within the campaign (If applicable)
activity_duration_ms	Length of time spent for the campaign activity in ms (If applicable)
correct_count	Number of questions answered correctly (If applicable)

start_date	Window Specifier. Will return only tags with creation timestamp greater than given
end_date	Window Specifier. Will return only tags with creation timestamp less than given

tag_name
tag_id
fan_id
creation_timestamp
first_name
last_name
email

include_recent_entry	Include latest campaign into payload on result
include_business_opt_ins	Include business opt ins into payload on result
name	Email, Phone, Display Name, or Fan ID of a fan.
crm_active_days
crm_inactive_days
crm_start_active_date
crm_end_active_date
fan_youngest_age
fan_oldest_age
fan_incl_snapshot_uids
fan_excl_snapshot_uids
fan_tags
include_tags	Include fan tags into payload on result
fan_tag_relations	Whether to include fans with tags related to those supplied in 'fan_tags' field
fan_networks
fan_only_filter	List. When given, search will return results where the given values are not null (or true). Valid Options are: 'is_subscribed', 'is_optout', 'is_phone_subscribed', 'phone', 'birth_date', 'gender', 'fan_source', 'country_code', 'province', 'metro_area', 'city', 'postal_code', 'latitude'
fan_not_only_filter	List. When given, search will return results where the given values are null (or false). Valid Options are: 'is_subscribed', 'is_optout', 'is_phone_subscribed', 'phone', 'birth_date', 'gender', 'fan_source', 'country_code', 'province', 'metro_area', 'city', 'postal_code', 'latitude'
fan_postal_codes
fan_radius_longitude	A valid longitude. Ex. 45.501. Must be accompanied by fan_radius_latitude and fan_radius_km.
fan_radius_latitude	A valid latitude. Ex. -73.57. Must be accompanied by fan_radius_longitude and fan_radius_km.
fan_radius_km	Must be given when supplying a single fan_postal_codes or when supplying a fan_radius_longitude and fan_radius_latitude
fan_provinces
fan_rating
fan_gender
fan_source
fan_metro_areas
fan_start_creation_date	Format YYYY-MM-DD
fan_end_creation_date	Format YYYY-MM-DD
idol_names
idol_relations
ticket_event_name
ticket_price_code
ticket_start_purchase_date
ticket_end_purchase_date
ticket_venue_name
ticket_venue_provinces
ticket_purchased_days
ticket_artist_name
ticket_start_event_date
ticket_end_event_date
ticket_seat_price_min
ticket_seat_price_max
ticket_seat_count_min
ticket_seat_count_max
ticket_sales_count_min
ticket_sales_count_max
ticket_is_negative
search_uid	If this parameter is supplied, we will continue returning records from previous search execution
limit	Maximum page size. Has to be less than a 1000
max_count	Maximum total number of records retrieved. Max value of 1,000,000. Default = 100,000

last_update_date	yyyy-mm-dd. Gets latest fans having last update date after this date.
min_time_key	The time key used to fetch the next page of updated fans. The format is '<unix_time>_<milliseconds>_<fan_id>'. Use the max_fan_time_key returned in the meta structure of previous request for fetching the next page.

fan_id
account_id
name
first_name
last_name
display_name
is_confirmed
is_phone_confirmed
email
province
latitude
longitude
creation_timestamp
ip_address
country_code
city
is_subscribed
is_optout
is_phone_subscribed
rating
phone
birth_date
metro_area
postal_code
last_update_timestamp
fan_source
fields
gender
tags
moderator_stats
has_password
props
is_guest
last_page_tab_id
last_campaign_name
opted_in_business_ids
creation_timestamp_iso
last_update_timestamp_iso

start_date *	yyyy-mm-dd
end_date *	yyyy-mm-dd
point_name *
performance_uid	Optional. Filter point counts by a specific performance.

purchase_key *	A unique key for this purchase, recommended format {network}-{order_key}-{line_item_id}
network *	The network that the purchase originated from.
order_key *	An identifier for the order. Typically, an order will have multiple order items / purchases.
merchant_key *	An identifier for a specific merchant/seller which made the sale.
order_timestamp *	The timestamp when the purchase was made.
gross_sale_amount *	The gross sale amount made on this purchase.
net_sale_amount *	The net sale amount made on this purchase.
location_key	An identifier for specific location that the purchase was made.
customer_key	An identifier for the customer of this purchase.
email	The customer's email.
phone	The customer's phone.
country	The customer's country, can be a country code or country name.
province	The customer's province i.e. British Columbia
city	The customer's city i.e. Vancouver
product_key	An identifier for the product attached to this purchase.
product_name	A human-readable name for the product.
product_category	The category that the product falls under.

network *	The network that the purchase originated from.
start_date *	All purchases made after this date will be returned.
end_date *	All purchases made before this date will be returned.
product_name	A product name, this field is a search field so all product names which contain this string will be returned.
merchant_key	Only return purchases which come from a specific merchant.
location_key	Only return purchases which are from a specific location.
next_purchase_key	Used for pagination, each response will contain a next_purchase_key field if there is more data to be fetched.

point_name
fan_id
fan_point_count	number of points based of filter
rank	rank of fan among all fans based on filter
display_name

purchase_key	A unique key for this purchase.
fan_id	The fan ID associated with this purchase.

account_id	The tradablebits account ID
network	The network that this purchase originates from.
purchase_key	A unique key for this purchase.
order_key	An identifier for an order, a single order may have multiple order items / purchases.
location_key	An identifier for a specific location.
merchant_key	An identifier for a specific merchant/seller.
customer_key	An identifier for the customer associated with this order.
fan_id	The fan ID associated with this purchase.
order_timestamp	The timestamp of the purchase as a unix timestamp.
gross_sale_amount	The gross sale amount made on this purchase.
net_sale_amount	The net sale amount made on this purchase.
deduction_amount	The amount deducted on this purchase such as discounts or refunds.
product_key	An identifier for the product attached to this purchase.
product_name	A human-readable name for the product.
product_category	The category that this product falls under.
email	The customer email associated with this purchase_key.
phone	The customer phone associated with this purchase_key.
country_code	The customer's country code.
province	The customer's province.
city	The customer's city.
order_timestamp_iso	The order timestamp in ISO format.

min_ticket_id	Window Specifier. Will return only tickets with ticket_id greater than given
max_ticket_id	Window Specifier. Will return only tickets with ticket_id less than given
min_purchase_date	Date filter option. Will return only tickets on or after a given date
max_purchase_date	Date filter option. Will return only tickets on or prior to a given date
min_last_update_date	Date filter option. Will return only tickets on or after a given date
max_last_update_date	Date filter option. Will return only tickets on or prior to a given data
email	Allows you to filter tickets to specific user/email address
limit	Max row count. Max. allowed value is 1000
data	Additional fields to include: supported value: fan
include_deleted	If set to true, return will include deleted tickets. Default = False

ticket_id	Unique Identifier for the ticket
ticket_key	Remote Tickey Key
account_id	Tradable Bits Acount ID
email	email on the ticket
customer_dsn	Identifies the tickets source
network	type of remote network to fetch ticket
event_key	Event Key in remote system
event_date	ISO date of the event
event_name	Event Name
purchase_timestamp	ISO Date
paid_amount	Total Paid Amount
order_amount	Full Order Amount
barcode	Wristband Barcode
lookup_id	Wristband Lookup ID
num_seats	Number of tickets/seats on the purchase
fan_id	Unique Fan Identifier
artist_name	Artist Name
price_code	Price Code or Level
venue_name	Name of Venue
city	City
province	Province or State
country_code	ISO country code
metro_area	DMA or CMA Area (Currently only for US/CA)
venue_province	Province or State of Venue
order_key	Identifier for the Order
ticket_category	Ticket Category
import_uid	Identifies the ticket import (if applicable)
postal_code	Postal Code / ZIP
customer_key	ID of customer in remote system
is_deleted	True if ticket deleted
ticket_type	Ticket Type
ticket_type_category	Category of Ticket Type
last_updated_timestamp	ISO date of last update
original_paid_amount	Full paid ticket amount before discounts or fees
original_order_amount	Full order amount before discounts or fees
original_num_seats	Original number of seats
status	Ticket Status
fan	Fan reference
section_name	Ticket Section Name
row_name	Ticket Row Name
seat_num	Ticket Seat Number
plan_event_key	Plan Event Name

first_name *
last_name *
email *
purchase_timestamp *	YYYY-MM-DD HH:MI:SS in GMT timezone
paid_amount *	Numeric value for line item
num_seats *	Number of seats purchased
event_date *	ISO8601 Encoded String
event_name *
phone
customer_key	Key of the customer in the remote system
ticket_key	Optional. Unique identifier for the line item (i.e. unique per price code and amount).
price_code	Optional. Price level or code of line item
is_subscribed	Subscribed to email
is_phone_subscribed	Subscribed to phone
city
province
postal_code
country_code
artist_name
venue_name
event_key
network
order_key
is_deleted	Boolean value
fan_source	Text identifier if fan is to be created

event_name	Must be exact name
event_key
event_date	Format YYYY-MM-DD
network
venue_name	Must be exact name
is_ticketless_only	Boolean, not allowed to be passed in combination with event_key, event_date, event_name or venue_name

event_uid	Unique identifier for the event
account_id
event_key
event_name
venue_name
artist_name
event_date
creation_timestamp
network
notes
label_name
event_type

action	create / update / delete, defaults to create
event_uid	Unique identifier for the event, REQUIRED for update/delete
event_name *	Must be exact name
event_key *
event_date *	Format YYYY-MM-DD
network *
venue_name
artist_name
notes
label_name
event_type

max_purchase_date *	Format YYYY-MM-DD
min_purchase_date *	Format YYYY-MM-DD
event_name	Must be exact name.
event_key
event_date	Format YYYY-MM-DD.
venue_name	Must be exact name
artist_name
event_specific	Format 'true' or 'false'. Determines whether new/returning stats are by date only or by event as well. Default = False

returning_fans_count
new_fans_count
sales_count
seats_count
revenue

account_id	Tradable Bits Account ID
registration_key	Unique Identifier for the registration
order_key	Remote Ticket Key
event_name
event_date	ISO date of the event
event_key
fan_id
registration_timestamp	Timestamp of registration. Unix Time
email	email on the ticket
venue_name
barcode
lookup_id
ticket_key
network
first_name
last_name
phone
address
city
country_code
province
postal_code
is_minor
birth_date
is_preferred
creation_timestamp	Timestamp of import. Unix Time
activity_id
is_subscribed
is_phone_subscribed
performance_uid	Performance UUID of the ticket event associated with the registration

scan_group_name *	scan_group_name / group_set_name identifier for different groups of scans.
start_date *	Scan creation start_date, scans between start_date and end_date will be fetched.
end_date *	Scan creation end_date, scans between start_date and end_date will be fetched
network *	The ticketing network.
next_scan_key	Used for pagination, each response will contain a 'next_scan_key' value which is to be supplied in the subsequent request in order to page through all records in the response. It does not need to be supplied on the first request to this endpoint.
venue_name	Venue name for the event.
event_date	Date of the event.

scan_key	An identifier associated with this scan
account_id	TradableBits account ID
network	Network associated with this scan
fan_id	Fan ID associated with this scan
event_key	The event key linked to this scan
is_success	Boolean field, represents whether the scan was successful
access_mode	The type of scan i.e. IN, OUT
scan_group_name	The group_set_name / scan_group_name for this scan.
site_name	Site name associated with this scan.
site_id	The integer ID for the site.
node_name
zone_name
scan_timestamp	The time that scan occurred
registration_key	The registration key.
ticket_order_key	The order key of the associated ticket.
event_name	The name of the event linked to the registration
event_date	The date of the event linked to the registration.
venue_name	Venue name linked to the registration
email
first_name
last_name
phone
country_code
province
postal_code
registration_timestamp	Timestamp when registration occurred
barcode	Wristband barcode associated with this scan/registration.

label_name	Limit Idols to a specific label
idol_uid	Filter by specific idol_uid

account_id
idol_uid
idol_name
idol_type
description
is_explicit	is_explicit flag
creation_timestamp
last_update_timestamp
idol_labels	An array of labels associated with this idol.

action *	add/delete
idol_uid	One of idol_uid or idol_name is required.
idol_name	Name for a given (as alternative to UUID). One of idol_uid or idol_name is required.
is_explicit	is_explicit boolean flag, optional.

limit	Record Limit
campaign_title	Limit results to specific campaign

campaign_title *	Name of custom campaign
field_<custom field name>	Additional meta data as per defined custom fields

crm_field_key
account_id
field_type
creation_timestamp
field_options
is_active
is_global