Skip to main content

Cadmium's Eventscribe

Cadmium's Eventscribe Integration Guide

Overview

This guide explains how to connect Bridged with Cadmium's Eventscribe to read event content including registrant profiles, exhibitor data, session information, and speaker details. The integration supports reading this data for activation, qualification, and nurture playbooks where event context is needed.

Eventscribe is designed for associations, automating logistics planning and managing abstract submissions alongside floor plans. It offers multiple API options for pulling data from its products, including the Developer Kit API (for lead retrieval) and Education Harvester API (for sessions/speakers) .

Primary Use Case: Read Event Content

For Bridged's event experience integrations, the primary use case is reading event-related data, including:

Data Type

Use in Bridged

Registrant/Attendee data

Personalize outreach and qualification conversations

Exhibitor data

Support exhibitor-related queries

Session data

Answer attendee questions about schedules

Speaker profiles

Provide speaker bios and session information

Booth/Floor plan data

Navigational assistance for attendees

⚠️ Important: API Access Model

Cadmium's Eventscribe API has a unique access model. Key points:

Consideration

Details

API access requires contracting

Access must be contracted per event, per third-party vendor

Cadmium does not do development

All integration development is done by the client or third-party vendor

Per-booth API keys

For lead retrieval (Developer Kit), each exhibitor booth gets a unique API key

Pagination required for large datasets

Methods returning large amounts of data require pagination

Rate limits enforced

1 call per minute for large methods; 1 call per second for others

Expiration date required

Must include sunset date in code (e.g., event end date)

Prerequisites

Before starting, ensure you have:

  • An Eventscribe account with the relevant product(s): Registration, Education Harvester, or Expo Harvester

  • API access contracted for your event (contact Cadmium Sales or your event organizer)

  • Your API credentials (API Key provided after contracting access)

  • For lead retrieval: Booth number and associated API key per exhibitor

Note: API credentials are unique per event, per third-party vendor. Cadmium will provide credentials and documentation after contracting .

Connection Methods

Method

Best for

Setup complexity

Data Access

Developer Kit API (Lead Retrieval)

Scanning attendee QR codes, pulling registrant profiles

Medium

Registrant demographic data

Education Harvester API

Session, speaker, and presentation data

Medium

Agenda, speakers, presentations

Expo Harvester API

Exhibitor, booth, and staff data

Medium

Exhibitor directory, booth maps

Registration Write Back (Cadmium-managed)

Automated data pushes from Eventscribe

Low (Cadmium manages)

Registration data to IdP

Manual Export (Excel/CSV)

One-time or backup data pulls

Low

Any data

Recommendation: Use direct API access for automated syncs. For organizations needing Eventscribe to push data, Cadmium offers a managed "Write Back" integration .

Step 1: Contract API Access

  1. Contact your event organizer or Cadmium sales representative to request API access

  2. Specify which Eventscribe products you need access to:

    • Registration API - For attendee/registrant data

    • Education Harvester API - For sessions, speakers, presentations

    • Expo Harvester API - For exhibitors, booths, staff

    • Developer Kit API - For lead retrieval (per exhibitor booth)

  3. Complete the API access contract (paid service)

  4. Cadmium will provide:

    • API Key(s) - One per event per vendor

    • API Documentation - Swagger/OpenAPI specification

    • Test Account GUID - For testing without live data

Step 2: Configure Bridged to Connect to Eventscribe API

For Developer Kit API (Lead Retrieval)

The Developer Kit API is used for scanning attendee badge QR codes to pull registrant profiles in real-time .

  1. Log in to your Bridged dashboard

  2. Navigate to the Integrations section. If you do not see this section, contact support@bridged.media

  3. Click Eventscribe → Connect Account → Developer Kit API

  4. Enter the following credentials:

Field

Description

API Key

Your unique per-booth API key (provided after contracting)

Base URL

Eventscribe API endpoint (provided in documentation)

Booth Number

For identifying the correct API key (if multiple booths)

  1. Click Connect

For Education/Expo Harvester APIs

  1. In Bridged, navigate to Integrations → Eventscribe → Connect Account

  2. Select Education Harvester API or Expo Harvester API

  3. Enter credentials provided by Cadmium:

Field

Description

API Key

Your event-specific API key

Base URL

Eventscribe API endpoint

Event ID

Your event identifier

  1. Click Connect

Step 3: Available API Endpoints

Developer Kit API - Registrant Lookup

Method

Description

Key Fields Returned

/v1/devkitapi/lookup

Look up registrant by QR code payload

firstName, lastName, pronouns, organization, position, phone, email, address, city, state, postalCode, countryCode

Request format:

bash

curl -X POST "https://api.eventscribe.com/v1/devkitapi/lookup" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"payload": "URL_ENCODED_QR_CODE"}'

Testing with Sandbox:
Use the test GUID 5aff520b-640d-47c4-9b83-a3eabe925952 as the payload to receive a test profile instead of live attendee data .

Education Harvester API

Method

Description

getPresentationsWithPresenters

Get all presentations with speaker details

getAllSpeakers

Get all speaker profiles

getSessions

Get session/agenda data

⚠️ Rate Limit: The getPresentationsWithPresenters method is limited to 1 call per minute. Pagination is required .

Expo Harvester API

Method

Description

getAllExhibitorsWithBooth

Get all exhibitors with booth assignments

⚠️ Rate Limit: This method is also limited to 1 call per minute .

General rate limits: For all other methods, limit is 1 call per second .

Step 4: Alternative - Cadmium-Managed Write Back Integration

If your organization prefers not to develop custom API code, Cadmium offers a managed integration service :

Registration Write Back

Cadmium pushes registration data to your system on a schedule:

  • Daily - Once per day

  • Weekly - Once per week

  • One-time - After event milestone or conclusion

Data includes: registrant profiles, purchase items, session registrations .

Expo Harvester Write Back

Cadmium pushes exhibitor, booth, and staff data to your system .

To set this up:

  1. Contact your Cadmium sales representative

  2. Provide technical documentation of your endpoint

  3. Provide sandbox/test environment (if available)

  4. Cadmium conducts feasibility analysis

  5. Cadmium develops and manages the integration on your behalf

Step 5: Alternative - Manual Export

If API access is not available or needed:

  1. Log in to your Eventscribe product

  2. Navigate to the relevant data section (Registrants, Exhibitors, Sessions)

  3. Use the Export to Excel function

  4. Upload CSV to Bridged via dashboard

Bulk sync limit: Each bulk operation is limited to 50 records per request.

Step 6: Configure Sync Settings

Setting

Options

Description

Data objects

Registrants, Exhibitors, Sessions, Speakers, Booths

Which event data to read

Sync frequency

Hourly, Daily, Weekly

How often to refresh data

Sync method

API Direct, Cadmium Write Back, Manual Export

Preferred access method

Expiration date

Event end date

Required for API calls to stop after event

Important: Your code must include a sunset/expiration date (typically the event end date) to ensure API calls aren't made unnecessarily after the event .

Common Use Cases

Playbook

How Event Data Is Used

Activation

Read registrant list to trigger pre-event reminders via WhatsApp

Qualification Agent

Read registrant profile data and session attendance for lead scoring

Nurture & Conversion

Read exhibitor and session data for post-event follow-up

Example Conversation Powered by Eventscribe Data

When an exhibitor scans an attendee's badge QR code, Bridged:

  1. Receives the QR code payload

  2. Calls the Developer Kit API /lookup endpoint with the exhibitor's API key

  3. Returns the attendee's profile data (name, company, title, contact info)

  4. Agent can engage in personalized conversation

Rate Limiting & Performance

Limit Type

Value

Heavy methods (getPresentationsWithPresenters, getAllExhibitorsWithBooth)

1 call per minute

All other methods

1 call per second

Data update frequency

New registrants appear in ~5 minutes

Pagination

Required for large datasets to prevent timeouts

Bulk operations

Maximum 50 records per request

Security & Permissions

  • Eventscribe uses API Key authentication via x-api-key header

  • API keys are unique per event, per vendor, and per booth (for Developer Kit)

  • Credentials are encrypted and never stored in plain text

  • All API calls should be made over TLS 1.2+

  • Cadmium reserves the right to revoke access for misbehaving applications

Troubleshooting

Issue

Likely cause

Solution

Connection fails (401)

Invalid API key

Verify API key with Cadmium; keys are event/vendor specific

No data returned (404)

Registrant not found

Wait 5 minutes for new registrations to sync; verify QR code is from correct event

Timeout

Large dataset without pagination

Implement pagination; use smaller batch sizes

Rate limiting (429)

Exceeding call limits

Respect 1 call/minute for heavy methods; 1 call/second for others

Data outdated

Updates take ~5 minutes

Account for delay in real-time expectations

Internal error (500)

API issue

Wait and retry; contact integrationservices@gocadmium.com if persists

Test mode needed

Live data not suitable for dev

Use test GUID 5aff520b-640d-47c4-9b83-a3eabe925952 for sandbox testing

Support

For integration support, contact your Bridged account manager or email support@bridged.media.

For Eventscribe-specific questions:

  • Integration Support: integrationservices@gocadmium.com

  • Email subject format: "[Event Name] Developer Kit API" with exhibitor name and booth number

  • Support hours: Monday – Friday, 8 am – 5 pm ET

  • Sales/Access questions: Contact your Cadmium sales representative