Create a service account for an integration

A service account gives an integration its own identity in one KORONA Event account. It has a name, a role and optional default point of sale. It uses API keys and has no email address or browser sign-in. Use a separate service account for each integration or location that needs different permissions or a different default POS.

Create the account

Account owners and platform administrators can create and manage service accounts.

1. Open Admin > Users and select Create service account.
2. Enter an Account name that identifies its purpose, such as “BookingKit — Berlin”.
3. Choose a Role with the permissions required by your integration. Confirm the required permissions with the connector provider.
4. Optionally choose a Default point of sale. This is used when the integration asks KORONA Event to choose a POS automatically. A matching order channel override or default can take precedence. An explicit POS supplied by the integration takes precedence over automatic selection.
5. Select Create service account. Its detail page opens with the Service account label.
6. Under API keys, select Create API key. Copy the new key immediately into your secret manager and configure the integration. The full key is shown only once.

No invitation or password setup is needed. Service accounts appear in the normal user list and can be selected when assigning an integration user to an order channel.

See Get API access for the API endpoint, account header and authentication example. Creating a service account does not activate the external connector or configure its products, channels or reseller billing assignments. For BookingKit, see Work with BookingKit bookings.

Maintain access

Open the service account under Admin > Users to change its default POS or manage its API keys. Role editing is available when role management is enabled for your account. Changes to the role affect the permissions of its API keys.

To replace a key, create a new one, configure the integration to use it, and then revoke the old key. If the new key was lost before it was stored, create another; the masked value cannot reveal it again.

To stop one credential, select Revoke API key beside it. To remove the service account's access to the account, select Delete on its detail page; this removes its membership and revokes its keys for the account. Historical order creator references are retained.

Service accounts cannot receive password-reset emails, accept invitations to another account, or be used to sign in to the back office. They do not receive user newsletters or changelog emails. Existing integration users remain unchanged; coordinate any migration with the connector owner so the current connection continues working.