All Collections
Security and Privacy
Event and Organization API Keys
Event and Organization API Keys

Important details to consider related to event and organization API keys

Troy Kasting avatar
Written by Troy Kasting
Updated over a week ago

The Attendease API is organized around the REST industry standard. Our API is designed to use resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP client. JSON will be returned in all responses from the API, including errors.

The Event API provides various means of reading and writing to your event. For Enterprise customers, we also offer an Organization API to access all events and attendees at the organization level.

The APIs provide access to organization and event data and should be carefully managed to ensure that data security and privacy is maintained.

Best practices related to event and organization API keys include:

  • Never share API keys with anyone since they act as passwords that provide programmatic access to your event data.

  • It is good practice to delete API keys if they are no longer needed (or contact support to request for them to be deleted in the case of Organization API keys).

  • It is good practice to regenerate API keys on occasion if access needs to be maintained over long periods of time (or request for them to be regenerated in the case of Organization API keys).

To delete or regenerate an Event API token,:

  • Navigate to the screen at Event -> Integrate -> Access Tokens

  • Find the token in question and click "Remove"

  • If you would like to generate a new token, click "Add Access Token"

To delete or regenerate your Organization API credentials:

  • Please Contact Support and one of our agents will be happy to assist.

Did this answer your question?