How to access attendee details of partnered events
Use this article when you need to download opted-in attendee exports or read the technical field guide for an event.detail.sharing.config row.
Treat this like crown-jewel data: if you would not print it and leave it on a train seat, do not copy it to unmanaged laptops.
Before you start
- Open Event registration sharing while signed in to your Climb account.
- Confirm with your legal/compliance owner that you may process attendee exports for the named event.
- Install a modern browser that allows CSV downloads without blocking pop-ups.
Who can do this
Only portal contacts with the Administrate Organization sub-user permission can load these routes; otherwise you are redirected to /my/company?error=not_admin.
Steps
- Open
Event registration sharingand read the grey intro sentence: exports only include registrations that satisfy the consent rule configured for your organisation on each event. - Locate the table with columns
Event,Configuration, andActions. - Press
CSVon the row you need—your browser downloadsevent_<event_id>_registrations.csvstraight away (no separate attendee grid inside the portal). - For machine-readable access, press
API docson the same row to openAPI documentation, then follow theAuthenticationandExport endpointssections using theBase URLpreformatted host. - Press
Credentialswhen you need the OAuth client id or to mint a new secret/API key. - Store any downloaded file in locations approved by your DPO; the CSV contains personal data subject to the event’s legal basis.
Check the result
- The CSV opens and each row lines up with registrations you expect for that configuration.
- You can explain which consent rule was applied using the wording from the list page.
If something does not work
- If the page shows <code>No sharing configurations are linked to your company yet.</code>, ask the organiser to publish a detail-sharing configuration tied to your commercial partner.
- If the CSV is empty except for headers, no registrations currently satisfy the configured consent filter—confirm the question/answers with the event team before assuming an outage.