What it does
The Abstracts module is designed for public-facing content: only abstracts with status acceptedare returned.
Use it for an "Abstracts" page, a PDF program book generator, or a mobile-app abstract browser.
Scopes
- abstracts:read – required
- abstracts:write – for submissions + uploads
Module gate: the Abstracts module must be enabled.
List accepted abstracts
/api/public/v1/abstracts/abstractsPagination supports limit and offset. Default limit is 50, max is 200. Ordering is newest first.
Get accepted abstract by ID
/api/public/v1/abstracts/abstracts/:abstractIdUse this for detail pages and deep links.
Include authors
Add include=authors (or the SDK param) to attach authors. This is convenient but can increase payload size.
Upload an attachment
/api/public/v1/abstracts/attachments/upload-urlThis mints a short-lived signed upload URL for abstract-attachments. Upload the bytes with PUT, then store the returned storageUriin your submission payload.
Submit an abstract
/api/public/v1/abstracts/submissionsSubmissions are scoped to a registrationId and respect the conference submission config (closed/deadline).
List submissions for a registration
/api/public/v1/abstracts/submissionsGet submission by ID
/api/public/v1/abstracts/submissions/:abstractIdProgram book tips
Fetch all accepted abstracts on the server, then render into HTML/PDF. For large conferences, paginate in batches of 200.
Abstract content is not ultra-real-time. Cache for minutes/hours and allow manual refresh.