This section provides endpoints to authenticate vFairs event. It covers how to get an access token, manage its lifecycle, and handle event-specific access. vFairs uses OAuth 2.0 to ensure secure and controlled API access, allowing applications to authenticate safely without exposing sensitive credentials.
Operations
Attendees
This section provides endpoints to manage event attendees, including registration field retrieval, attendee creation, updates, bulk/group registrations, resume uploads, and user deletions. Secure access requires event-specific OAuth tokens. The API supports dynamic form configurations, pagination, filtering by email or user_id, and nested child_users for structured group registrations.
Operations
Session Tracks
This section provides endpoints to create, update, retrieve, and delete session tracks for multi-language events. Use track_id=0 for new tracks. Tracks require language-specific mapping via /v5/event/languages. Supports pagination, filtering, and bulk retrieval to efficiently manage localized session tracks.
Operations
Sessions
This section provides endpoints to create, update, retrieve, and delete event sessions. Use session_id=0 for new entries. Sessions can be linked to session tracks and speakers via their IDs and require language-specific entries via /v5/event/languages for multi-language support. The API supports pagination, filtering, and bulk data retrieval for efficient session management.
Operations
Session Handouts
This section provides endpoints to create, update, retrieve, and delete session handouts. Use session_handout_id=0 for new entries. Handouts are linked to sessions via their IDs, which can be retrieved from /v5/sessions. The API supports pagination, filtering, bulk retrieval, and document management to ensure seamless attendee access.
Operations
Speakers
This section provides endpoints to create, update, retrieve, and delete speaker profiles. Use speaker_id=0 for new entries. Speakers can be linked to sessions via their IDs, retrieved from /v5/sessions. The API supports dynamic form configurations, including fields like company_name and bio, and allows image handling, session associations, and deletions by speaker_id, email, or session_id.
Operations
Event
This section provides endpoints to retrieve event metadata, including available languages for multi-language configuration and detailed event information. These endpoints are essential for localizing content such as sessions and tracks and integrating event-specific settings to ensure a seamless and customized event experience.
Operations
Reports
This section provides endpoints to retrieve reports of the events
Operations
Get QR Scan Analytics
Request
This endpoint is used to retrieve QR scan analytics data for the event. You can filter the results by registration fields, user type, date range, specific users, and sort by scan time. The response includes details about who scanned whom and when.
Query
pageinteger
Page number for pagination
Example: page=1
limitinteger
Number of records per page
Example: limit=10
registration_fieldsstring
Comma separated string of registration field IDs
Example: registration_fields=123,123
user_typestring
Filter by user type: ALL, Attendee, Admin, Event Owner, Booth Admin
This endpoint retrieves user journey analytics data for the event. Either user_id or email is mandatory to retrieve the data. Start date and end date should be in YYYY-MM-DD format. Activity Types must be one of: NAVIGATION, CHAT, SCAVENGER_HUNT, WEBINAR, VIDEO, BOOTH_VISIT, BOOTH_LINK, DOCUMENT, SWAG_BAG, LOGIN, CMS_PAGE, BOOTH_BANNER, or ALL to get all records. The show_only_live parameter will filter to show only live event's user journey analytics.
Query
pageinteger
Page number for pagination
Example: page=1
limitinteger
Number of records per page
Example: limit=10
user_idinteger
User ID. Either user_id or email is mandatory.
Example: user_id=1234875612
emailstring(email)
Email of the user. Either user_id or email is mandatory.
Example: email=demo@vfairs.co
start_datestring
Start date in YYYY-MM-DD format
Example: start_date=2022-06-07
end_datestring
End date in YYYY-MM-DD format
Example: end_date=2022-06-07
activity_typesstring
Filter by activity types. Must be one of: NAVIGATION, CHAT, SCAVENGER_HUNT, WEBINAR, VIDEO, BOOTH_VISIT, BOOTH_LINK, DOCUMENT, SWAG_BAG, LOGIN, CMS_PAGE, BOOTH_BANNER, or ALL to get all records.