talque
  • External integrations for talque
  • JSON API (readonly)
    • General
      • Locales and Text
    • Organization
      • Read
    • Lecture
      • List
      • Read
      • Files
      • Authorization
    • Speaker
      • List
      • Read
      • Authorization
    • Participants
    • Vendors
      • List
      • Read
      • Authorization
    • Room
      • List
      • Read
    • Enumerations
      • Locale
  • Deep links
    • General
    • Organization
    • Profile links
    • Lecture links
    • Partner links
    • Post links
    • Map links
    • Video rooms
  • Webhooks
    • General
    • Authentication
    • File upload
    • Users
    • Invites
    • Tickets
    • Vendors
      • Create
      • Update
      • Delete
    • COMING SOON: Announcements
    • COMING SOON: Lectures
    • Map Data
      • Map layer
      • Map features
      • Update references
  • COMING SOON: Chat Bots
  • Wordpress Plugin
    • Installation
    • Pages
    • Shortcodes
      • Filters
      • Optional settings
    • Routing
    • Configuration
  • Javascript plugin
    • Introduction
    • Installation
      • Initial page
      • Filters
      • Optional settings
    • Routing
    • Configuration
  • Single Sign-On
    • OAuth2 Login
    • Website data
    • OAuth2 Flow
      • Request an Authorization Code
      • Exchange for Access Token
      • Authorized Requests
  • SELF-SERVICE LINKS
    • Event Ticket Token
  • Old Wordpress Plugin
    • Download
    • Pages
    • Shortcodes
    • Filter Options
    • Style Options
  • Old Javascript Plugin
    • Introduction
    • Routing
    • Installation
  • Troubleshooting
    • Firewall Configuration
  • Talque Plugin
    • Download
    • Installation
    • Configuration
Powered by GitBook
On this page

Was this helpful?

  1. Webhooks

Tickets

The tickets webhook is for ticket shops and other existing event ticketing systems to connect attendee ticket information to talque. Tickets can provider users access to the talque digital platform, as well as specific talks, webinars, etc. depending on the ticket category.

Tickets can be uploaded through the webhook one or more at a time, along with an optional purchase order for those tickets. The purchase order upload is not currently the complete data for the upload, but just to track the provenance of the tickets and who purchased them.

Add ticket(s) and purchase order

POST https://talque.com/webhook/org/:orgId/ticket

Path Parameters

Name
Type
Description

orgId*

string

The talque ID of your event

Request Body

Name
Type
Description

tickets*

array

Array of ticket objects with properties:

extTicketId: (required) Your internal identifier for the ticket

email: For personalized tickets, the e-mail address of the ticket holder

firstName: First name of the ticket holder; must only be provided if a personal e-mail is provided

lastName: See firstName

phoneNumber: Ticket holder phone number in international E. 164 format (+<country code><phone number>)

phoneNumberType: Either "MOBILE" or "FIXED", if known

companyName: Ticket holder company, if any

jobTitle: Ticket holder job title, if any

extUserId: External ticketing provider's user ID for the ticket holder, if any

tickets: An array of identifiers of the type of ticket (e.g. "day pass", "full event", etc.); this is an event-specific identifier that must be coordinated with talque; may be zero or more

eventIds: Array of talque session IDs for sessions to which the ticket grants access

extEventIds: Array of your internal identifiers for session add-ons to tickets. This can be passed if the talque IDs are not known by the system.

vendorIds: Array of talque vendor IDs for companies/exhibitors of which the ticket holder is a representative.

extVendorIds: If the ticket holder is a representative of a company or exhibitor, this is an array of strings providing the internal identifiers of those companies, in case the talque IDs are not known by the system.

purchaseOrder

object

Optional purchase order details associated with the ticket or tickets' purchase. This property may be omitted entirely if not relevant. It has the following properties:

extPurchaseId: (required) For ticketing providers, your internal identifier for the purchase order

email: The e-mail address of the ticket purchaser

firstName: First name of the ticket purchaser

lastName: See firstName

companyName: Ticket purchaser company, if any

jobTitle: Ticket purchaser job title, if any

{
    // Response
}
{
    // Response
}
{
    // Response
}
PreviousInvitesNextVendors

Last updated 9 months ago

Was this helpful?