We released an update to options 1 and 4 of the Presentation API, which allows the inclusion of the Date Created and Date Last Updated fields of a media item. The abstract body is part of the “get” method of the Presentation API call. Finally, limits to how often any of the APIs can be called have been rolled out as well.
As a refresher, the set of Application Programming Interfaces offered as part of the cAPI module offer integration points that customers can use to import to, update and read from the CTI products. These interfaces are typically used to create live integrations with association management systems, registration systems, disclosure systems and transfer data to and from non-CTI abstract management systems, non-CTI presentation management systems, and non-CTI virtual system meetings. APIs typically have a set of capabilities for data creation, reading, updating, and deleting that are different from the specific workflow rules in an application. While some APIs, such as the registration, AMS, and disclosure APIs, are used for live ‘real-time’ integrations, other APIs, such as Meeting Set-up, Session data management, and Presentation data management, are used to move data in bulk safely and efficiently from one system to another system. Greater flexibility exists for reading data while creating, updating, and deleting application workflow rules control data. API limits are placed on the Meeting Set-up, Session data management, and Presentation data management APIs to ensure that the interfaces are used as designed (for data transfer) and not as a hosting platform.
This cAPI update is targeted to add functionality to the “read” function and will not support creating, updating, or deleting Date Created, Date Last Updated for media items or AbstractBody within a submission. Workflow rules within the CTI application control these.
Each API within cAPI has its own documentation set, and the updated document can be found on the knowledge base under “APIs” and under “Developer Documentation”.
cAPI functionality will continue to be developed, and roadmap items exist to support (1) clients pushing their previously created abstracts from a foreign system into cOASIS subject to cOASIS workflow rules, (2) clients pushing their previously created media items into cAdmin from a foreign system subject to the cAdmin media item template conversion rules.