This integration is powered by Singer's Club Speed tap. For support, visit the GitHub repo or join the Singer Slack.
Club Speed integration summary
Stitch’s Club Speed integration replicates data using the Club Speed API . Refer to the Schema section for a list of objects available for replication.
Club Speed feature snapshot
A high-level look at Stitch's Club Speed integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release Status |
Released |
Supported By | |
| Stitch Plan |
Free |
Singer GitHub Repository | |
| DATA SELECTION | |||
| Table Selection |
Supported |
Column Selection |
Supported |
| REPLICATION SETTINGS | |||
| Anchor Scheduling |
Supported |
Advanced Scheduling |
Unsupported |
| Table-level Reset |
Unsupported |
Configurable Replication Methods |
Unsupported |
| TRANSPARENCY | |||
| Extraction Logs |
Supported |
Loading Reports |
Supported |
Connecting Club Speed
Club Speed setup requirements
To set up Club Speed in Stitch, you need:
-
A Club Speed API key. To use Stitch’s Club Speed integration, you’ll need an API key generated by Club Speed. Reach out to Club Speed support to have them generate this credential for you.
After you’ve received the API key, you can complete the setup in Stitch.
Step 1: Add Club Speed as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Club Speed icon.
-
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Club Speed” would create a schema called
stitch_club_speedin the destination. Note: Schema names cannot be changed after you save the integration. - In the Club Speed Subdomain field, enter your Club Speed subdomain. For example: If the full subdomain were
stitchdata.clubspeedtiming.com, you’d only enterstitchdatainto this field. - In the Club Speed Private Key field, paste your Club Speed private API key. Note: You’ll need to contact Club Speed to obtain this credential.
Step 2: Define the historical sync
The Sync Historical Data setting will define the starting date for your Club Speed integration. This means that:
- For tables using Incremental Replication, data equal to or newer than this date will be replicated to your data warehouse.
- For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Club Speed’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Step 3: Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Club Speed integrations support the following replication scheduling methods:
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Initial and historical replication jobs
After you finish setting up Club Speed, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Club Speed table schemas
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs > customers), while case is maintained in PostgreSQL destinations (CusTomERs > CusTomERs). Refer to the Loading Guide for your destination for more info.
booking
| Replication Method : |
Full Table |
Primary Key  :
|
onlineBookingsId |
The booking table contains info about bookings. A booking record exposes a heat to the online booking inerface in Club Speed.
|
onlineBookingsId
The ID for the booking. Reference: |
|
heatId
The heat ID for the booking. Reference: |
|
isPublic
Indicates whether the booking is available to the online booking interface. |
|
productsId
The ID of the product for the booking. Reference: |
|
quantityTotal
The total number of booking reserverations to make available. |
booking_availability
| Replication Method : |
Full Table |
Primary Key :
|
heatId |
The booking_availability table contains info about the current availability for online bookings. These take into account both online and local booking reservations.
|
heatId
The heat ID for the booking. Reference: |
|||||||
|
heatDescription
The description of the heat. |
|||||||
|
heatSpotsAvailableCombined
The heat ID for the booking. Reference: |
|||||||
|
heatSpotsAvailableOnline
The number of spots to be exposed to the online interface for the entire heat. |
|||||||
|
heatSpotsTotalActual
The original number of total spots for the heat. |
|||||||
|
heatStartsAt
The start time for the heat. |
|||||||
|
heatTypeId
The heat type ID. Reference: |
|||||||
|
isPublic
Indicates whether the booking should be made available in the online booking interface. |
|||||||
|
products
A list of products associated with the booking.
|
check_details
| Replication Method : |
Key-based Incremental |
Replication Key  :
|
createdDate |
|
Primary Key :
|
checkDetailId |
||
The check_details table contains info about line items and quantity info attached to checks.
createdDate as the Replication Key. This means that check details will be selected for replication only when they are initially created. Any subsequent updates made to the check detail will not be detected, as the createdDate value will not be updated. Refer to the Key-based Incremental Replication documentation for more info and examples.
|
checkDetailId
The check detail ID. Reference: |
|
createdDate
The timestamp when the check detail was created. |
|
calculateType
The type of application for an applied discount. |
|
checkId
The ID of the parent check for the check detail. |
|
discountApplied
The amount of the discount applied to the check detail. |
|
discountDesc
The description of the applied discount. |
|
discountId
The ID of the applied discount. Reference: |
|
discountNotes
Notes about the discount application. |
|
discountUserId
The ID of the user who applied the discount. Reference: |
|
g_CustId
The ID of the customer on which to apply points on purchase. Note: This may reference a gift card. Reference: |
|
g_Points
The amount of money to be given to the customer ( |
|
gst
The percent of the tax to be applied as GST. |
|
m_DaysAdded
|
|
p_CustId
The ID of the customer on which to apply points on purchase. Reference: |
|
p_Points
The number of points to be applied on purchase. |
|
productId
The ID of the product on the check detail. Reference: |
|
productName
The name of the product on the check detail. |
|
qty
The quantity of the product on the check detail. |
|
r_Points
The number of reservation points to be applied on purchase. |
|
s_CustId
Reference: |
|
s_NoOfLapsOrSeconds
|
|
s_SaleBy
|
|
s_Vol
|
|
status
The status of the check detail. Possible values are:
|
|
taxId
The ID of the tax to be applied to the check detail. Reference: |
|
taxPercent
The percent of tax to be applied. |
|
type
The type of the product. Possible values are:
|
|
unitPrice
The unit price of the product. |
|
unitPrice2
The unit price of the product. |
|
voidNotes
Notes added while voiding the check detail. |
checks
| Replication Method : |
Key-based Incremental |
Replication Key :
|
closedDate |
|
Primary Key :
|
checkId |
||
The checks table contains info about checks, or financial invoices, that have been closed.
closedDate as the Replication Key. This means that checks will not be selected for replication until the record has a closedDate value, which should occur when the check has a status of closed.
|
checkId
The check ID. Reference: |
|
closedDate
The timestamp when the check was closed. |
|
broker
The name of the check broker. |
|
customerId
The ID of the customer for the check. Reference: |
|
discount
The discount applied to the entire check. |
|
discountId
The ID of the discount applied to the check. Reference: |
|
discountNotes
Notes about the discount applied to the check. |
|
discountUserId
The ID of the user who applied the discount. Reference: |
|
fee
The additional fee to be applied to the entire check. |
|
gratuity
The gratuity to be applied to the whole check. |
|
invoiceDate
The timestamp on which the invoice was handled. |
|
isTaxExempt
Indicates if the entire check is exempt from taxation. |
|
name
The name of the check. |
|
notes
Any notes about the check. |
|
openedDate
The timestamp on which the check was opened. |
|
status
The status of the check. Possible values are:
|
|
total
The applied total for the check. This includes all underlying check details, taxes, discounts, fees, and gratuity. |
|
type
The type of the check. Possible values are:
|
|
userId
The ID of the user who created the check. Reference: |
customers
| Replication Method : |
Key-based Incremental |
Replication Key :
|
lastVisited |
|
Primary Key :
|
customerId |
||
The customers table contains info about the customers for a location.
lastVisited as the Replication Key. This means updated customer data will only be selected for replication when the lastVisited value for the customer’s record is updated.
|
customerId
The customer ID. Reference: |
|
lastVisited
The date on which the customer last visited. |
|
Address
The first address line for the customer. |
|
Address2
The second address line for the customer. |
|
City
The city of residence for the customer. |
|
Country
The country of residence for the customer. |
|
Custom1
Custom data holder 1. |
|
Custom2
Custom data holder 2. |
|
Custom3
Custom data holder 3. |
|
Custom4
Custom data holder 4. |
|
LicenseNumber
The license number for the customer. |
|
State
The state of residence for the customer. |
|
Zip
The post code for the address of the customer. |
|
accountCreated
The timestamp when the customer record was created. |
|
birthdate
The customer’s birth date. |
|
cardId
The membership card number for the customer. |
|
company
The company of the customer. |
|
creditLimit
The credit limit for the customer. |
|
creditOnHold
Indicates whether the customer’s credit is on hold. |
|
deleted
Indicates whether the customer has been soft deleted. |
|
donotemail
Indicates whether the customer wishes to receive emails. |
|
email
The email addresss of the customer. |
|
fax
The fax number of the customer. |
|
firstname
The customer’s first name. |
|
gender
The customer’s gender. Possible values are:
|
|
generalNotes
Any notes about the customer. |
|
howdidyouhearaboutus
The ID of the source for the customer. Reference: |
|
ignoreDOB
Indicates whether the customer’s birth date can be ignored. |
|
isEmployee
Indicates if the customer is also an employee. |
|
isGiftCard
Indicates if the customer record should be considered a gift card. |
|
lastname
The customer’s last name. |
|
memberShipTextLong
Description of the membership for the customer. |
|
membershipStatus
The customer’s membership status. |
|
membershipText
Abbreviation of the membership for the customer. |
|
mobilephone
The mobile phone for the customer. |
|
originalId
|
|
phoneNumber
The phone number for the customer. |
|
phoneNumber2
The alternate phone number for the customer. |
|
priceLevel
The price level that this customer’s membership type grants to the customer. |
|
privacy1
Indicates whether the name of the customer should be hidden from race results. |
|
proskill
The current proskill for the customer. |
|
racername
The nickname for the customer. |
|
status1
Indicates a specific status. This is customizable per venue to handle indicators such as Customer added from POS, Customer added from Online Event Registration, Customer signed secondary waiver, etc. |
|
status2
See |
|
status3
See |
|
status4
See |
|
totalRaces
The total number of times this customer has raced. |
|
totalVisits
The total number of times this customer has visited. |
|
waiver
Indicates the primary waiver the customer has signed. |
|
waiver2
Indicates the secondary waiver the customer has signed. |
|
webUserName
|
discount_types
| Replication Method : |
Full Table |
Primary Key :
|
discountId |
The discount_types table contains info about discount types.
|
discountId
The discount ID. Reference: |
|
amount
The amount of the discount. Refer to |
|
calculateType
The calculation type for the discount, which determines how
|
|
deleted
Indicates whether the discount has been soft deleted. |
|
description
The description for the discount. |
|
enabled
Indicates whether the discount is currently enabled. |
|
needApproved
Indicates whether the discount should require manager approval. |
|
productClassId
The product class that is applicable for the discount. Reference: |
event_heat_details
| Replication Method : |
Key-based Incremental |
Replication Key :
|
added |
|
Primary Key :
|
customerId : eventId |
||
The event_heat_details table contains info about customers who have been placed in a queue for a specific event.
|
customerId
The ID of the customer in the queue. Reference: |
|
eventId
The ID of the event. Reference: |
|
added
The date at which the customer was added to the event queue. |
|
proskill
The proskill for the customer. |
|
roundLoseNum
The round at which the customer dropped out of the event. |
|
totalRaces
The total number of races in the event. |
event_heat_types
| Replication Method : |
Full Table |
Primary Key :
|
eventHeatTypeId |
The event_heat_types table contains info about event type classifications, which are used to look up event_rounds when creating events.
|
eventHeatTypeId
The event heat type ID. |
|
cadetsPerHeat
The maximum number of cadet racers for an event round. |
|
description
The description of the event round. |
|
eventTypeId
The event type for the default event round information. Reference: |
|
heatTypeId
The heat type to be used with the resulting heat. Reference: |
|
heatsPerRacer
The number of heats in which each racer will participate. |
|
racersPerHeat
The maximum number of racers for the event round. |
|
roundNumber
The ordered round number in the event. |
event_reservation_links
| Replication Method : |
Full Table |
Primary Key :
|
eventReservationLinkId |
The event_reservation_links table contains lists of check and reservation IDs, or checks that are linked to event reservations.
|
eventReservationLinkId
The event reservation link ID. |
|
checkId
The ID of the check to be linked to an event reservation. Reference: |
|
reservationId
The ID for the event reservation to which the check is linked. Reference: |
event_reservation_types
| Replication Method : |
Full Table |
Primary Key :
|
eventReservationTypeId |
The event_reservation_types table contains info about the descriptions for event reservation types.
|
eventReservationTypeId
The event reservation type ID. Reference: |
|
description
The description of the event reservation type. |
event_reservations
| Replication Method : |
Key-based Incremental |
Replication Key :
|
startTime |
|
Primary Key :
|
eventReservationId |
||
The event_reservations table contains info about event reservations, which are linked to events.
startTime as the Replication Key. This means that unless an event reservation’s startTime is updated, changes to event reservation records will not be selected for replication.
|
eventReservationId
The event reservation ID. Reference: |
|
startTime
The expected start time of the event reservation. |
|
allowOnlineReservation
Indicates whether reservations can be made online. |
|
deleted
Indicates whether the event reservation has been soft deleted. |
|
description
The description for the event reservation. |
|
endTime
The time at which the event reservation is expected to end. |
|
eventTypeId
The ID for the event type of the event. Reference: |
|
externalSystemId
A field for storing an external reference for the event reservation. |
|
isEventClosure
|
|
mainId
The ID for the parent event reservation. Reference: |
|
minNoOfAdultsPerBooking
The minimum number of customers per booking. |
|
noOfRacers
The current number of booked customers. |
|
notes
The notes for the event reservation. |
|
ptsPerReservation
The number of points required to make a reservation. |
|
repId
|
|
status
The index for the event status of the event reservation. |
|
subject
The name for the event reservation. |
|
typeId
The event reservation type ID. Reference: |
|
userId
The ID of the user that made the event reservation. Reference: |
event_rounds
| Replication Method : |
Full Table |
Primary Key :
|
eventRoundId |
The event_rounds table contains info about event rounds. This table acts as a link between events and their corresponding rounds in the heat_main.
|
eventRoundId
The event round ID. Reference: |
|
cadetsPerHeat
The maximum number of cadet racers for the event round. |
|
eventId
The ID of the parent event. Reference: |
|
heatDescription
The description of the heat. |
|
heatTypeId
The heat type ID of the heat. Reference: |
|
heatsPerRacer
The number of heats in which each racer will participate. |
|
racersPerHeat
The maximum number of racers for this event round. |
|
roundNumber
The ordered round number in the event. |
event_statuses
| Replication Method : |
Full Table |
Primary Key :
|
eventStatusId |
The event_statuses table contains info about event statuses, which are statuses assigned to event_reservations.
|
eventStatusId
The event status ID. |
|
colorId
The ID of the color which will be used to highlight the event when given this status |
|
seq
The order in which the event status appears in dropdowns. |
|
status
The readable description of the status. |
event_task_types
| Replication Method : |
Full Table |
Primary Key :
|
eventTaskId |
The event_task_types table contains info about event task types, which are event_tasks to be tracked for completion.
|
eventTaskId
The event task ID. Reference: |
|
deleted
Indicates whether the event task has been soft deleted. |
|
description
The description of the task type. |
|
name
The name of the task type. |
|
seq
The sequence in which the task type should appear. |
event_tasks
| Replication Method : |
Key-based Incremental |
Replication Key :
|
completedAt |
|
Primary Key :
|
eventTaskId |
||
The event_tasks table contains info about the tasks to be completed for a given event_reservation.
|
eventTaskId
The event task ID. Reference: |
|
completedAt
The date on which the task was completed. This field will be populated only if the task has been completed. |
|
completedBy
The ID of the user that completed the task. This field will be populated only if the task has been completed. Reference: |
|
eventReservationId
The ID of the event reservation. Reference: |
|
eventTaskTypeId
The event task ID. Reference: |
event_types
| Replication Method : |
Full Table |
Primary Key :
|
eventTypeId |
The event_types table contains info about event types.
|
eventTypeId
The event type ID. Reference: |
|
deleted
Indicates if the event type was soft deleted. |
|
description
The description of the event type. |
|
displayAtRegistration
Indicates whether the event type should show during registration. |
|
enabled
Indicates whether the event type is currently enabled. |
|
eventTypeName
The name of the event type. |
|
eventTypeTheme
The theme of the event type. |
|
memberOnly
Indicates whether or not a membership is required for this event type. |
|
onlineProductId
The ID of the product used to purchase the event. Reference: |
|
ptsPerReservation
The number of points required per reservation. |
|
trackId
The ID of the track for which this event can be added. Reference: |
events
| Replication Method : |
Key-based Incremental |
Replication Key :
|
eventScheduledTime |
|
Primary Key :
|
eventId |
||
The events table contains info about events.
eventScheduledTime as the Replication Key. This means that unless an event’s eventScheduledTime value is updated, changes to event records will not be selected for replication.
|
eventId
The event ID. Reference: |
|
eventScheduledTime
The scheduled time for the event. |
|
createdHeatSpots
The number of heat spots that have been created for the event. |
|
createdHeatTime
The time at which the relevant heat will start. |
|
eventDesc
The description of the event. |
|
eventDuration
The expected duration of the event, in minutes. |
|
eventNotes
The notes for the event. |
|
eventTheme
The theme for the event. |
|
eventTypeId
The ID for the event type. Reference: |
|
eventTypeName
The name of the type of the event. |
|
memberOnly
Indicates whether entry into the event requires a membership. |
|
reservationId
The ID of the reservation for the event. Reference: |
|
totalRacers
The total number of racers for the event. |
|
trackNo
The number of the track to be used for the event. |
gift_card_history
| Replication Method : |
Key-based Incremental |
Replication Key :
|
transactionDate |
|
Primary Key :
|
giftCardHistoryId |
||
The gift_card_history table acts as a transactional log for keeping track of each change that occurs with gift cards.
customer. This means that each gift card identifier should be considered a customerId in this table.
|
giftCardHistoryId
The gift card history ID. |
|
transactionDate
The date at which the transaction occurred. |
|
checkDetailId
The check line item that resulted in this change. Reference: |
|
checkId
The check which resulted in this change. Reference: |
|
customerId
The holder of the gift card. Note: This may correspond to either a standard gift card or a member card on a customer account. Reference: |
|
ipAddress
The IP address of the machine from which the change originated. |
|
notes
Any notes for the transaction. |
|
points
The number of changed points for this transaction. |
|
type
The type of the transaction. Possible values are:
|
|
userId
The ID of the user that recorded the transaction. Reference: |
heat_main
| Replication Method : |
Key-based Incremental |
Replication Key :
|
finish |
|
Primary Key :
|
heatId |
||
The heat_main table contains info about finished heat mains, which are instances of races on the standard venue calendar.
finish as the Replication Key. This means that only finished heat mains will be selected for replication.
|
heatId
The heat ID. Reference: |
|
finish
The actual finish time of the heat. |
|
beginning
The actual start time of the heat. |
|
eventRound
The ID of the event round which corresponds to the heat. Reference: |
|
heatColor
An integer representation of the color to be used on the heat calendar. |
|
lapsOrMinutes
The quantity of laps or minutes (depending on heat type) required for the heat to finish. |
|
memberOnly
Indicates whether a heat should only allow entrance to members. |
|
notes
Notes for the heat. |
|
numberOfReservation
The number of additional reservations for the heat. Note: These typically represent purchased slots in a heat. |
|
pointsNeeded
The number of points required to enter the heat. |
|
raceBy
The indication of whether the heat will treat the value of
|
|
racersPerHeat
The total number of racers available for the heat. |
|
scheduleDuration
The expected duration of the heat. |
|
scheduledTime
The scheduled start time of the heat. |
|
speedLevel
The speed level for the heat. |
|
status
The status of the heat. Possible values are:
|
|
track
The ID for the track for the heat. Reference: |
|
type
The heat type for the heat. Reference: |
|
winBy
The indication of whether the heat is won by laps or position. Possible values are:
|
heat_main_details
| Replication Method : |
Key-based Incremental |
Replication Key :
|
heat_main.finish |
|
Primary Key :
|
heatId : customerId |
||
The heat_main_details table contains info about customers that were entered into finished heats.
|
heatId
The heat ID. Reference: |
|
customerId
The customer ID. Reference: |
|
autoNo
The kart number for the customer. Note: This is not assigned until during/after the heat. |
|
finishPosition
The finish position for the customer. |
|
firstTime
Indicates whether or not this is the customer’s first race. |
|
groupFinishPosition
The finish position of the customer relative to their group. |
|
groupId
The ID of the group the racer belongs to. |
|
lineUpPosition
The line up position scheduled for the customer. |
|
pointHistoryId
The ID of the point history utilized to add this customer to the heat. |
|
positionEditedDate
The timestamp at which the position was edited. |
|
proskill
The proskill of the customer. |
|
proskillDiff
The amount at which the proskill of the customer changed as an outcome of the heat. |
|
scores
|
|
timeAdded
The time at which the customer was added to the heat. |
|
userId
The ID of the user that added the customer to the heat. Reference: |
heat_types
| Replication Method : |
Full Table |
Primary Key :
|
heatTypesId |
The heat_types table contains info about heat types.
|
heatTypesId
The heat type ID. Reference: |
|
cannotBelow
The minimum cut off for lap times, in milliseconds. |
|
cannotExceed
The maximum cut off for lap times, in milliseconds. |
|
cost
The number of points required for the heat type. |
|
deleted
Indicates whether the heat type has been soft deleted. |
|
enabled
Indicates whether the heat type is enabled. |
|
isEventHeatOnly
Indicates whether the heat type is meant only for events. |
|
isPracticeHeat
Indicates whether this heat type is meant to be a practice round. |
|
lapsOrMinutes
The quantity of laps or minutes (depending on the heat type) required for the heat type to finish. |
|
memberOnly
Indicates whether a heat type should only allow entrance to members. |
|
name
The name of the heat type. |
|
raceBy
Indicates whether the heat type should treat
|
|
racersPerHeat
The total number of racers available for the heat type. |
|
scheduleDuration
The expected duration of the heat type. |
|
speedLevel
The speed level for the heat type. |
|
trackId
The default track ID for the heat type. Reference: |
|
winBy
The indication of whether the heat type is won by laps or position. Possible values are:
|
membership_types
| Replication Method : |
Full Table |
Primary Key :
|
membershipTypeId |
The membership_types table contains info about memberships.
|
membershipTypeId
The membership type ID. Reference: |
|
description
The description of the membership type. |
|
enabled
Indicates whether the membership type is currently enabled. |
|
expirationType
The number of days when this membership will expire. |
|
expires
Indicates whether or not the membership should ever expire. |
|
priceLevel
The price level that this membership type would grant to a customer. |
|
seq
The sequence in which the membership type should appear in a dropdown. |
memberships
| Replication Method : |
Key-based Incremental |
Replication Key :
|
changed |
|
Primary Key :
|
customerId : membershipTypeId |
||
The memberships table contains info about memberships, which is a pairing of a customer and membership_type.
|
customerId
The customer ID. |
|
membershipTypeId
The membership type ID. |
|
changed
The date at which the membership last changed. |
|
byUserId
The ID of the user who created the membership. Reference: |
|
expiration
The date at which the membership will expire. |
|
notes
Any notes about the membership. |
payments
| Replication Method : |
Key-based Incremental |
Replication Key :
|
payDate |
|
Primary Key :
|
paymentId |
||
The payments table contains info about collected payments.
|
paymentId
The payment ID. Reference: |
|
payDate
The timestamp at which the payment was collected. |
|
cardType
The type of credit card used to make the payment. This will usually be populated only if |
|
checkId
The ID of the check for which payment was applied. Reference: |
|
customerId
The ID of the customer that made the payment. Reference: |
|
extCardType
The card or payment processor type for the payment. |
|
payAmount
The monetary amount of the payment. |
|
payStatus
The status of the payment. Possible values are:
|
|
payTax
The monetary amount of the payment which was applied to tax. Note: |
|
payTerminal
The terminal at which the payment was collected. |
|
payType
The type of the payment which was collected. Possible values are:
|
|
transaction
A reference to a transaction number, typically one which was returned from a third party processor. |
|
userId
The ID of the user that created the payment. Reference: |
|
voidDate
The timestamp at which the payment was voided. |
|
voidNotes
The notes as to why the payment was voided. |
|
voidTerminal
The terminal where the payment was voided. |
|
voidUser
The ID of the user that voided the payment. Reference: |
payments_voided
| Replication Method : |
Key-based Incremental |
Replication Key :
|
voidDate |
|
Primary Key :
|
paymentId |
||
The payments_voided table contains info about voided payments.
|
paymentId
The payment ID. Reference: |
|
voidDate
The timestamp at which the payment was voided. |
|
cardType
The type of credit card used to make the payment. This will usually be populated only if |
|
checkId
The ID of the check for which payment was applied. Reference: |
|
customerId
The ID of the customer that made the payment. Reference: |
|
extCardType
The card or payment processor type for the payment. |
|
payAmount
The monetary amount of the payment. |
|
payDate
The timestamp at which the payment was collected. |
|
payStatus
The status of the payment. Possible values are:
|
|
payTax
The monetary amount of the payment which was applied to tax. Note: |
|
payTerminal
The terminal at which the payment was collected. |
|
payType
The type of the payment which was collected. Possible values are:
|
|
transaction
A reference to a transaction number, typically one which was returned from a third party processor. |
|
userId
The ID of the user that created the payment. Reference: |
|
voidNotes
The notes as to why the payment was voided. |
|
voidTerminal
The terminal where the payment was voided. |
|
voidUser
The ID of the user that voided the payment. Reference: |
product_classes
| Replication Method : |
Full Table |
Primary Key :
|
productClassId |
The product_classes table contains info about classes applied to products. Product classes determine how products are aggregated in Club Speed’s reporting system.
|
productClassId
The product class ID. Reference: |
|
deleted
Indicates whether the product class has been soft deleted. |
|
description
The description of the product class. |
|
exportName
The export name to be used when building exports from reports. |
products
| Replication Method : |
Full Table |
Primary Key :
|
productId |
The products table contains info about products.
|
productId
The product ID. Reference: |
|
deleted
Indicates whether the product has been soft deleted. |
|
description
The description of the product. |
|
enabled
Indicates whether the product is currently enabled. |
|
g_Points
The amount of gift card points provided when this product is purchased. |
|
p_Points
The number of points provided when this product is purchased. |
|
price1
The price of the product. |
|
price2
|
|
priceCadet
|
|
productClassId
The ID of the reporting product class for the product. Reference: |
|
productType
The type of the product. Possible values are:
|
|
r_Points
The amount of reservation points provided when this product is purchased. |
|
taxId
The tax ID for the product. Reference: |
reservations
| Replication Method : |
Key-based Incremental |
Replication Key :
|
createdAt |
|
Primary Key :
|
onlineBookingReservationsId |
||
The reservations table contains info about reservations. Reservations are indications that a customer is looking to purchase a spot in a booking or has already purchased a spot.
createdAt as the Replication Key. This means that reservations will be selected for replication only when they are initially created. Any subsequent updates made to the reservation will not be detected, as the createdAt value will not be updated. Refer to the Key-based Incremental Replication documentation for more info and examples.
|
onlineBookingReservationsId
The online booking reservation ID. Reference: |
|
createdAt
The timestamp at which the reservation was created. |
|
checkId
The ID of the check for the reservation. Reference: |
|
customersId
The ID of the customer for the reservation. Reference: |
|
expiresAt
The timestamp at which the reservation will be automatically expired, if the status ( |
|
onlineBookingReservationStatusId
The ID for the status of the reservation. Statuses should be set to Temporary while the underlying kart is open, and set to Permanent after the purchase has been made. Possible values are:
|
|
onlineBookingsId
The ID of the booking for the reservation. Reference: |
|
quantity
The quantity of reservations to hold. |
|
sessionId
An optional session identifier to be used for documentation and debugging purposes, typically generated by an external website. |
sources
| Replication Method : |
Full Table |
Primary Key :
|
sourceId |
The sources table contains info about how customers find and register at venues.
|
sourceId
The source ID. Reference: |
|
deleted
Indicates whether the source has been soft deleted. |
|
enabled
Indicates whether the source is currently enabled. |
|
locationId
The ID of the venue location the source applies to. |
|
name
The name of the source. |
|
seq
The sequence in which the source should display in a dropdown. |
| Replication Method : |
Full Table |
Primary Key :
|
taxId |
The taxes table contains info about tax calculations, which are typically applied to products.
|
taxId
The tax ID. Reference: |
|
amount
The percentage of the tax. For example: |
|
deleted
Indicates whether the tax has been soft deleted. |
|
description
The description of the tax. |
|
gst
The percentage of the tax which should be considered GST, where applicable. |
| Replication Method : |
Full Table |
Primary Key :
|
userId |
The users table contains info about employees and system users. Note: While some employees may also be customers, this table does not contain customer information.
|
userId
The user ID. Reference: |
|
cardId
The card ID for the user. |
|
deleted
Indicates whether the user has been soft deleted. |
|
email
The email address for the user. |
|
empStartDate
The date on which the user started employment. |
|
enabled
Indicates whether the user is currently enabled. |
|
firstname
The user’s first name. |
|
isSystemUser
Indicates whether the user is a system/application user or a track employee. |
|
lastname
The user’s last name. |
|
phone
The user’s phone number. |
|
username
The user’s username. |
| Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.