How to use the API to retrieve a JSON response

Use this article when you need to call the JSON export route with optional incremental filters.

Before you start

• Open Event registration sharing while signed in to your Climb account.
• Know which consent-driven fields your integration needs so you can map JSON keys without guessing.

Who can do this

Steps

1. Authenticate using OAuth2 (preferred) or API key mode as described in API documentation → Authentication.
2. Issue GET <base>/api/event/detail-sharing/v1/registrations with your bearer token.
3. Append optional query parameters documented in the same page: updated_since, state, and include_write_date (all formats are spelled out in the table there).
4. Inspect the JSON object keys event_id, oauth_client_id, count, and registrations to validate you are reading the correct configuration.

Check the result

• The JSON parses and each registration object includes the expected attendee fields.
• The HTTP status is 200 and caching headers match your integration expectations.

If something does not work

• If count is 0 but the portal CSV shows rows, you likely filtered too aggressively with updated_since—widen the window.
• If you get HTML instead of JSON, you are hitting a login page—confirm the bearer token header is present and spelled Authorization.

Notes

Example once you have a token:

curl -sS "BASE/api/event/detail-sharing/v1/registrations?state=open,done" \
  -H "Authorization: Bearer ACCESS_TOKEN"