cAPIs Introduction

The cAPI integration points are powerful tools to help customers transfer data to and from CTI applications, customer-owned applications, and third parties. Like many powerful tools, they can also cause damage if used in a way other than intended. cAPI integration points are meant for transferring data and are not intended to provide live production hosting of customer data for other third parties. The current CRM pricing levels established for cAPI are intended only for data transfer use.

The cAPI integration points are powerful tools to help customers transfer data to and from CTI applications, customer-owned applications, and third parties. Like many powerful tools, they can also cause damage if used in a way other than intended. cAPI integration points are meant for transferring data and are not intended to provide live production hosting of customer data for other third parties. The current CRM pricing levels established for cAPI are intended only for data transfer use.

LIMITS

The limits apply to unique endpoints. The client would be able to request the same Presentation 3 times per hour since the PresentationID is included in the GET Presentation endpoint.

Request Limits
The limits are currently set to:
1. CREATES to 100reqs/1min
2. UPDATES to 1req/1min
3. GET to 3req/60min
4. DELETE to 3req/60min

These limits are applied to the complete URL of the endpoint. Ex:
https://sandbox.abstractsonline.com/capi/meeting/123/sessions/123/presentations/123 can be called with the above-mentioned limits across the different “methods”.

This allows the API developers to pull all Sessions/Presentations 3 times per hour without running into a rate limit. If they try to pull the same Presentation more than 3 times in a single 60-minute period, they will get a 429 – Too Many Requests response.

For this reason, we recommend storing a local cache of the SessionType/ActivityType/Location data (Key and Name) to prevent unnecessary queries of the Program Setup endpoints.

This would allow the API user to pull Program Data as frequently as every 20 minutes without exceeding rate limits.

Onsite Presentation Management Application: Hardware, Software & Network Requirements

CTI’s Presentation Management application is a scalable, cloud-based SaaS application allowing presenters to upload presentation files via the internet, make final updates and practice in an on-site speaker ready room, and then present from a local computer in a session room. In venues with stable, high bandwidth internet connections the onsite presentation management installation will only require hardware for session room computers and speaker ready room computers. In venues with unstable or insufficient bandwidth internet connections, an on-site caching server is available.

CTI’s Presentation Management application is a scalable, cloud-based SaaS application allowing presenters to upload presentation files via the internet, make final updates and practice in an on-site speaker ready room, and then present from a local computer in a session room.  In venues with stable, high bandwidth internet connections the onsite presentation management installation will only require hardware for session room computers and speaker ready room computers.  In venues with unstable or insufficient bandwidth internet connections, an on-site caching server is available.

The Presentation Management application supports streaming to overflow rooms and streaming to 3rd party content distribution platforms.

The Presentation Management application supports recording of streams to allow content to be edited and re-purposed.  Editing tools are available in the application and 3rd party video editing tools may be used as well.

Please refer to the application Knowledge Base for current Presentation Management documentation, network estimation tools, set-up guides and related API documentation.

Caching Server Setup v1.9

The document below is a step-by-step guide for setting up an onsite caching server. This server is used for onsite events to enable faster uploads and access to presentation files, especially in cases where network speeds are limited. It also facilitates quicker access to last-minute presentation uploads. The server setup manages the subsequent publishing of locally uploaded or updated files to the cloud server, which controls the delivery of presentations to connected applications.

The document below is a step-by-step guide for setting up an onsite caching server. This server is used for onsite events to enable faster uploads and access to presentation files, especially in cases where network speeds are limited. It also facilitates quicker access to last-minute presentation uploads. The server setup manages the subsequent publishing of locally uploaded or updated files to the cloud server, which controls the delivery of presentations to connected applications.

Caching Server FAQs
1. What are the advantages of using a caching server as opposed to not using one?
Using a caching server offers several benefits. Firstly, it accelerates file uploads within the local network. After uploading, you can promptly access the file from the caching server within the session room, even as the caching server syncs data over a slower internet connection. Furthermore, the file doesn’t need to be re-downloaded. In contrast, if you don’t utilize the caching server, the file must be uploaded from the speaker ready room to AWS, and then the session room downloads it from AWS. The caching server conserves bandwidth.
2. Does the presence of a caching server improve internet performance?
Yes, the presence of a caching server can lead to improved internet performance.
3. When should an association consider implementing a caching server?
A caching server is recommended for use when you want to optimize file transfer efficiency and save on bandwidth, particularly in scenarios where quick access to recently uploaded files is essential.