API Access

API Access

The API Access tab in Tickera Settings allows you to create and manage API keys for external communication with Tickera. These keys enable secure communication between Tickera and integrations such as mobile check-in apps (including Checkinera), third-party systems, or custom automation that relies on Tickera’s API.

API keys control who can access event, attendee, and ticket information and what level of permissions they have. Each key can be created, edited, or revoked at any time, giving you full control over access to your ticketing data.

How API access works with WooCommerce

Even when Tickera is used together with Bridge for WooCommerce, the API Access functionality remains exactly the same as in standalone Tickera. WooCommerce handles the checkout and order process, but Tickera continues to manage events, ticket generation, attendees, and check-ins — and therefore also controls API communication.

The API communicates with Tickera, not WooCommerce, so nothing changes in this area.

What remains the same

All features of the API Access tab behave exactly as they do in standalone Tickera:

• API keys are created under Tickera -> Settings -> API Access
• API keys authenticate requests made to Tickera’s API
• These keys are used by Tickera check-in apps
• WooCommerce plays no role in API permissions, behavior, or data access

If you’ve used API Access before enabling Bridge for WooCommerce, everything will work exactly as it did before.

What changes with Bridge for WooCommerce

Nothing.

API Access is entirely a Tickera feature. Bridge for WooCommerce does not alter, extend, or replace any part of the API functionality.

Summary

The API Access tab works identically whether Tickera is used on its own or together with Bridge for WooCommerce. API keys are still created and managed in Tickera Settings, and the API communicates directly with Tickera regardless of WooCommerce’s presence.