FAQ & Troubleshooting

Answers to common questions and solutions to issues you may encounter when integrating the Tickets SDK.

Frequently Asked Questions

Where do I get an API key?

API keys are issued by Ticketmaster as part of the integration onboarding process. You can explore available APIs and request access through the Ticketmaster Developer Portal.

For a production API key scoped to the Tickets SDK, contact your Ticketmaster integration representative directly. The Developer Portal key is for general API access and is not the same credential used to initialize the SDK.

What platforms and minimum OS versions are supported?

Platform	Language	Minimum Version
iOS	Swift	Xcode 26.2+, iOS 17+
Android	Kotlin	API 28 (Android 9.0)
React Native	TypeScript	See platform minimums above

React Native support requires the Ticketmaster NPM wrapper library. See Getting Started — React Native for setup instructions.

How do I report an issue or get support?

For integration questions and account-specific issues, contact your Ticketmaster integration representative.

For SDK bugs or unexpected behavior, you can open an issue on the relevant GitHub repository:

When reporting an issue, include the SDK version, platform and OS version, a minimal reproduction case, and any relevant error output or logs.

How do I support multiple teams in my app?

If your app serves fans from more than one team or venue, you can configure multiple API keys — one per team — and switch between them without requiring the user to log out. This uses ephemeral authentication sessions scoped to each team's backend.

For a full explanation and code examples, see the Multi-Team Authentication section in the Authentication examples article.

Can I use the SDK in a React Native app?

Yes. The Tickets SDK is available for React Native through an NPM wrapper library that bridges the native iOS and Android implementations.

See Getting Started — React Native for installation steps and configuration.

Common Issues

My app crashes on launch after adding the SDK

Check the following:

Frameworks not embedded: On iOS, ensure all required xcFrameworks are set to "Embed & Sign" in your target's Frameworks, Libraries, and Embedded Content settings. Frameworks set to "Do Not Embed" will cause a crash at runtime.
Authentication SDK not initialized: The Authentication SDK must be fully configured before you initialize the Tickets SDK. If you call the Tickets SDK initializer before TMAuthentication is set up, the SDK has no valid session to work with.
Wrong API key or region: An API key issued for one region (e.g., US) used with a different region configuration will cause the SDK to fail during initialization. Verify your key matches your target deployment region.

Login fails or shows a blank screen

Invalid API key: Double-check that your API key is correct and has been activated for SDK use by your integration representative.
Wrong environment: Confirm whether your build is targeting Production or Staging. A Staging API key will not work against the Production environment and vice versa.
Missing intent filter or URL scheme (Android): The Authentication SDK uses a redirect URI to return the user after OAuth login. If the intent filter for your app's redirect URI is missing or misconfigured in your AndroidManifest.xml, the login flow will not complete and the user will see a blank or stalled screen. Verify your intent filter matches the redirect URI configured for your API key.

Tickets don't appear after login

No purchased tickets on the account: The signed-in account may not have any tickets for upcoming events. Test with an account that has active orders.
API key does not have access to the correct backend: If your fans' tickets are on an Archtics backend but your API key is only configured for Host, the SDK will authenticate successfully but return no ticket inventory. Confirm with your integration representative which backends your key is authorized for.
Check the console for error messages: The SDK logs diagnostic messages that identify authentication errors, empty responses, and backend connectivity issues. Review the Xcode console (iOS) or Logcat (Android) output for error codes or descriptive messages that narrow down the cause.