Eventscribe REST API Overview

Overview

Developers can create their own integrations using our powerful APIs! An API (Application Programming Interface) is a software interface that allows an application to access data and interact with EventTech products and data. A developer can write code to create functions between a third-party application and our system to either push data (i.e., registration company pushing registrant data to Eventscribe fields) or pull data (i.e., AV company pulling speaker data from Education Harvester fields).

Our APIs can be accessed directly by a client’s in-house development team or third-party application vendor. Once contracted, Cadmium will provide API credentials and documentation. 

Available APIs

Below is a list of our APIs. Once contracted, Cadmium will reach out to provide API credentials. You'll send the credentials and documentation, available in the 'API Documentation' section of the knowledge area, to your third-party vendor. 

• EdgeReg (pull)
• Scorecard (pull)
• Education Harvester (pull)
• Expo Harvester (pull)
• Eventscribe Website & Mobile App (push)

API Access - Data Pull

A third-party is pulling data FROM an EventTech product. This is most common for Education Harvester. 

• Cadmium does not do any development. All development is completed by the client's in-house development team or third-party application.
• The client is responsible for working with its third-party to decide which available API fields to pull data from. 
• The client’s third-party is responsible for reading and understanding the API documentation and its available methods.
• The client may request API consultation to answer specific questions about the API functionality by contacting integrationservices@gocadmium.com. API consultation is billed at an hourly rate to the client.

API Access - Data Push

A third-party is pushing data TO an Eventscribe product. This is most common for Eventscribe.

• Cadmium does not do any development. All development is completed by the client's in-house development team or third-party application.
• The client is responsible for working with its third-party to decide which available API fields to push data to. 
• The client’s third-party is responsible for reading and understanding the API documentation and its available methods.
• The client is responsible for reviewing and testing all incoming data to verify accuracy and for testing the full end-user experience.
• The client may request API consultation by contacting integrationservices@gocadmium.com. API consultation is billed at an hourly rate to the client.
• Vendors that have pushed to the Eventscribe API in the past:
  • Badge Guys
  • eventPower
  • MCI
  • Showcare
  • Spargo

Pricing

API access is unique per event, per third-party and is contracted at a fixed rate. An hourly fee is charged if consultation is needed by your third-party; we recommend budgeting for three hours of consultation time just in case. Speak to your account manager for current pricing. 

API credentials are meant to be shared with one third-party vendor per event. 

We charge for access to our public APIs because there are many costs associated with offering this option to our clients and their third-party vendors, including but not limited to on-going development and updates, maintenance, monitoring, security, developer documentation, infrastructure, etc. 

As a reminder, downloading your data via a report is always an option at no charge.

Rate Limiting

To ensure the health and accessibility of our APIs, Cadmium monitors traffic and reserves the right to impose a rate limit or revoke access to any misbehaving application with excessive API usage. A rate limit is a specified number of API requests an application or user can make within a defined time frame.

• When using certain methods, such as getPresentationsWithPresenters, that return a large amount of data, it’s crucial to use pagination to prevent timeouts and reduce data transfer size; this is noted in the API documentation
• A rate limit of one call per minute is enforced for the getPresentationsWithPresenters and or getAllExhibitorsWithBooth methods
• For all other methods, a rate limit of one call per second is enforced
• It’s mandatory to include an expiration or sunset date in your code, usually set as the event’s end date, to ensure that API calls aren’t made unnecessarily beyond that point