Skip to content

Knowledge base/API

API V0.1

Jan 12

API Access

API Access is controlled by each Currinda site. Each client will provide OAuth Client ID and Client Secret information.

Authentication

Authentication to the API is through OAuth2.

Token Endpoint

https://{currinda_site_domain}/api/token

Authorize Endpoint

https://{currinda_site_domain}/api/authorize

Scopes

The only scopes available currently are for events and organisations, these are: event-{event_id} these allow access to an authenticated delegate's registration details for the specified event and org-{organisation_id} which is for the organisation membership details.

The following outlines the information supplied by the API endpoints for event and organisation. You must have authenticated for the pertaining scope to access this data.

Registration Details

Endpoint:

https://{currinda_site_domain}/api/event/{event_id}

Membership Details

Endpoint:

https://{currinda_site_domain}/api/organisation/{organisation_id}

Membership Status

There are a number of different statuses that maybe applicable to a membership:

  1. unapproved (the member has not been checked by an admin)
  2. pending (the member has been checked and has payments pending)
  3. outstanding (the member has outstanding invoices, maybe expired or not)
  4. expire (the member is none of the above and their expiry date is in the past)
  5. current (the member is current)

Logging Out

Logging out of connected websites is an important function so that people who are on shared computers can ensure their privacy. The connecting website should logout (clear the session of the exisiting user) and then redirect to https://{currinda_site_domain}/logout?redirect={return_url}