> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server. # What is the difference between ticketing APIs, SDKs and webhooks? > Compare ticketing APIs, SDKs and webhooks, including when each is used for event discovery, checkout, order updates and app integrations. **A ticketing API lets software request data or actions from a ticketing system; an SDK provides reusable developer code for working with supported interfaces; and a webhook delivers a notification when a configured event occurs.** They solve different integration problems and are often used together. An API is the interface, an SDK is a development aid, and a webhook is a way for one system to tell another that something happened. None of the three necessarily gives unrestricted access to ticket inventory or purchasing. ## What is a ticketing API? **A ticketing API is a defined interface through which approved software can retrieve ticketing information or request authorised operations.** A venue app might ask for event dates and ticket availability; a partner system might use permitted booking functions. The software usually initiates the request. A booking platform can ask, for instance, for events linked to a particular venue and receive structured information it can display. Some APIs offer only discovery information. Others expose reservation or purchase actions to contracted partners. Ticketmaster publicly distinguishes its Discovery API from a restricted Partner API that supports reservation and purchase functions. That illustrates why 'API access' is not a single level of capability. ## What is a ticketing SDK? **A software development kit (SDK) packages tools, code or components that help developers integrate functionality into an application.** An SDK may include an API client, authentication helpers, typed data objects, examples or visual components. For example, a JavaScript SDK might handle the mechanics of calling a ticketing API, while a seating component lets developers add a ready-made seat-selection interface to a website. The SDK does not necessarily replace the API; it can provide a simpler way to use it. Some ticketing SDKs consist mainly of API wrappers. Others provide substantial user-interface functionality, device access or native mobile capabilities. Developers need to check the SDK's platform support, version compatibility and maintenance history. ## What is a ticketing webhook? **A ticketing webhook sends an HTTP notification to another system when a predefined event occurs, such as an order being completed or a ticket being scanned.** The receiving application does not need to continuously ask whether anything has changed. A CRM integration might receive an order-completed notification, then update the customer's purchase history. The webhook may contain the needed information or simply enough identifiers for the CRM to request current details through an API. Webhook delivery is not the same as a guaranteed, immediate database update. Deliveries can be delayed, repeated or missed if the receiving system is unavailable. Integrations need appropriate authentication, retry handling and reconciliation. ## APIs vs SDKs vs webhooks: how do they compare? | Technology | Main job | Typical direction | Ticketing example | | ----------- | ---------------------------------------------- | ----------------------------------- | --------------------------------------------- | | **API** | Request data or an authorised action | App → ticketing service | Check availability or request a basket | | **SDK** | Make development simpler or provide components | Developer code using an API/service | Add seating UI or call endpoints with helpers | | **Webhook** | Notify another application about an event | Ticketing service → receiving app | Tell a CRM an order was completed | A webhook can be used without an SDK. An SDK may include API clients but no webhooks. And an API can work perfectly well when no event notifications are configured. The distinction matters because developers sometimes try to use polling when event notifications would be more suitable, or expect a webhook to make a booking modification that actually requires an API call. ## How do APIs, SDKs and webhooks work together? Consider an illustrative membership application that offers members access to selected concerts. 1. The app uses an API, perhaps through an SDK, to retrieve eligible events and current ticket options. 2. A customer selects tickets. A permitted API operation or hosted checkout creates the basket and completes the order. 3. The ticketing system confirms the purchase. 4. A webhook notifies the membership application that the order is complete. 5. The application may call the API again to obtain the authoritative order state before adding the purchase to the member's account. ![Sequence between a membership app and a ticketing system: 1, the app uses the API, perhaps through an SDK, to get eligible events; 2, an API operation or hosted checkout creates the basket and completes the order; 3, the ticketing system confirms the purchase; 4, a webhook notifies the app that the order is complete; 5, the app calls the API for the authoritative order state.](/_fern-files/nuweb-group.docs.buildwithfern.com/d65b26deb89db7dd7da7e7f84bd3e869f54573be2d8d73a1ff86d74d49254227/assets/diagrams/api-webhook-sequence.svg) This separation reduces unnecessary polling and prevents the membership application from assuming that displaying an item, reserving it and completing payment are equivalent operations. ## Can webhooks replace ticketing APIs? **Webhooks complement APIs rather than replacing them.** A webhook reports a change. An API lets an application ask a question or request an operation. For example, an order-completed webhook might arrive twice because the receiver did not acknowledge the first delivery. A robust integration records the event identifier or checks the order's final state before applying side effects twice. If the receiver loses a webhook or is unavailable for an extended period, it may need an API-based reconciliation job or another supported recovery mechanism. Developers should ask providers about signing secrets, event identifiers, retries, ordering guarantees and replay tools. ## When should developers use an SDK rather than calling an API directly? **Use a maintained SDK when it reduces routine integration work without hiding critical transaction behaviour.** Typed clients and tested authentication helpers can speed development, especially across several applications. Calling the API directly may make more sense when the SDK does not support the required language, the current API version or a needed capability. It can also be appropriate for a small server-side integration that uses only a few operations. Neither route removes the need to understand permissions, stock reservation, timeouts and error handling. A developer should be able to inspect what the SDK actually sends and how it behaves when the API fails. ## What should businesses ask an integration provider? Ask for the specific API operations available to your account, the SDKs that are actively maintained and the events supported by webhooks. Test how authentication, rate limits and permissions behave in a sandbox. Pay particular attention to the difference between an inventory enquiry and a reservation request. A displayed ticket can cease to be available before the customer reaches checkout. A webhook saying an order has completed is useful only when the integration also knows how to process that event safely. **The simplest useful model is this: APIs do work on request; webhooks announce events; SDKs help developers build with the available interfaces.** ## Related explanations #### [What is a ticketing webhook?](/apis-integrations/what-is-a-ticketing-webhook) APIs & Integrations · API fundamentals #### [What is a ticketing SDK?](/apis-integrations/what-is-a-ticketing-sdk) APIs & Integrations · API fundamentals #### [What is an API-first ticketing platform?](/apis-integrations/what-is-an-api-first-ticketing-platform) APIs & Integrations · API fundamentals #### [Hosted vs embedded vs headless ticketing: what is the difference?](/apis-integrations/hosted-vs-embedded-vs-headless-ticketing-what-is-the-difference) APIs & Integrations · Headless and embedded delivery [More in APIs & Integrations →](/apis-integrations)