API keys – create and manage

An API key is a digital access key. It allows external applications to securely access selected data from your Eventfrog account – for example, to automatically update events or connect different systems. You decide whether to use a key, which permissions it has, and how long it remains valid.

Where can I find the API keys?

You can manage your API keys in your account under «Settings» and the menu item «API keys». The list shows all API keys you have created – including the name, key type, validity period and the date of last use. You can edit existing keys as long as they have not yet reached their maximum validity period, and adjust the displayed name or expiry date.

This means you can:

• create keys
• view existing keys
• check expiry dates
• edit labels
• copy the key

A link to the technical API documentation is always visible on this page. For security reasons, the actual key is never displayed in plain text. Only when you explicitly click «Show API key» will it appear in a secure window, where it can be copied.

Create an API key

During the creation process, you first select the key type. Depending on its intended use, the key can provide read-only access or also allow editing and deleting your event data. Optionally, you can add a label to help you easily identify what the key is used for later on. Finally, set the expiry date and create the key with a single click. The key will appear immediately in the overview.

How it works:

1. Click «Create API key»
2. Select the key type (e.g. read-only or edit/delete)
3. Enter a label (optional)
4. Set the expiry date
5. Confirm the process

Overview of key types

There are three key types: the Public API key for reading public event data, the Organiser API key with read-only access, and the Organiser API key with read, write and delete permissions. In addition, there is a so-called embed key, which is automatically generated when you embed the Eventfrog ticket shop. This key is not shown in the overview and cannot be used for API requests.

Each API key automatically expires on the stored date. We will notify you by email in advance – 14 days, 7 days and 1 day before expiry. These reminders include the name and type of the key, as well as a link to its management. For security reasons, the key itself is never sent by email. After expiry, a key remains visible for a further twelve months but can no longer be used or edited. It is then automatically hidden.

Grant access to third parties

If you want to grant access to external parties, you can create a suitable API key yourself and share it. Organiser keys always apply exclusively to events you have created. For example, if an agency needs to retrieve data or manage content, you define the access rights via the key.

To prevent misuse, there are automatic limits on how often a key can be used. Per user account, a maximum of 30 requests per minute and 2,000 requests per day are permitted – regardless of how many API keys exist. All access is technically logged and monitored.

Existing API keys

If you have used API keys in the past, they have been migrated automatically. Keys that were used only for ticket shop embeds have been assigned the type “Embed”. Keys that accessed event data via the API have been classified as “Public API”. If a key previously served both purposes, we will create a new key for public use and inform you accordingly.

Technical URL

The Eventfrog APIs are available at:

api.eventfrog.net