What it does
Exhibition data is meant to be public-facing. Only exhibits that are marked as published are returned.
Typical uses: “Exhibitors” page, “Sponsors” grid, booth directory, or mobile app booth browser.
Scopes
- exhibition:read – required
- exhibition:write – required for submissions + uploads
Module gate: Exhibition must be enabled.
List exhibits
/api/public/v1/exhibition/exhibitsUses limit and offset (default 100, max 500). Results are ordered by published_at newest first.
Upload payment proof (optional)
/api/public/v1/exhibition/submissions/payment-proof/upload-urlOnly needed if the conference requires a proof image/file for exhibition submission fees. Request a signed upload URL, PUT the file, then pass the returned storage:// URI in payment.paymentProofUrl when submitting.
Submit an exhibit
/api/public/v1/exhibition/submissionsSubmits an exhibit application. Requirements depend on the conference settings (submission window, optional registration requirement, fee rules).
Sponsor page patterns
Render cards using title, short_description, and cover_image_url.
Use booth_code and location fields to power maps and venue signage.