> 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. # APIs & Integrations > Learn how ticketing APIs, webhooks, SDKs and embedded components connect ticketing systems with websites, apps and other business software. **Ticketing integrations let other software exchange information and permitted actions with a ticketing system.** A venue's app might read event availability, a membership service might recognise a signed-in member, and a finance system might receive completed orders. What an integration can do depends on the interfaces the provider exposes and the permissions granted to that integration. ## Start here #### [What is a ticketing API?](/apis-integrations/what-is-a-ticketing-api) Learn how event ticketing APIs connect event, availability and booking data with websites and apps, plus the difference between APIs, webhooks and SDKs. #### [What is headless ticketing?](/apis-integrations/what-is-headless-ticketing) Understand headless ticketing architecture, how APIs connect a custom frontend to ticketing services, and its benefits, limits and alternatives. #### [What is embedded ticketing?](/apis-integrations/what-is-embedded-ticketing) How embedded ticketing works inside websites and apps, the main integration approaches, and the difference between embedded, hosted and headless ticketing. #### [What is the difference between ticketing APIs, SDKs and webhooks?](/apis-integrations/ticketing-apis-vs-sdks-vs-webhooks) Compare ticketing APIs, SDKs and webhooks, including when each is used for event discovery, checkout, order updates and app integrations. #### [Hosted vs embedded vs headless ticketing: what is the difference?](/apis-integrations/hosted-vs-embedded-vs-headless-ticketing-what-is-the-difference) Compare hosted, embedded and headless ticketing models by control, implementation effort and ownership. ## Key ideas in this subject #### APIs, webhooks and SDKs do different jobs An API answers requests, a webhook reports that something happened, and an SDK makes an API easier to use. Many integrations combine all three. #### Reading data is not the same as changing it Permission to list events may not include reserving or ordering. Showing a seat as available does not hold it; only a reservation or booking does. #### There is more than one way to connect a journey Teams can build against APIs, embed a ready-made component, or hand the customer to a hosted checkout. Each moves work between business and provider. #### Access should be as narrow as the job requires Credentials decide which events, customers and actions an integration can reach. Granting only what it needs limits damage if something goes wrong. ## Reading paths All 21 explanations in APIs & Integrations, in 4 reading paths. #### 1 · API fundamentals * [What is a ticketing API?](/apis-integrations/what-is-a-ticketing-api) * [What is the difference between ticketing APIs, SDKs and webhooks?](/apis-integrations/ticketing-apis-vs-sdks-vs-webhooks) * [What is a ticketing webhook?](/apis-integrations/what-is-a-ticketing-webhook) * [What is a ticketing SDK?](/apis-integrations/what-is-a-ticketing-sdk) * [What is an API-first ticketing platform?](/apis-integrations/what-is-an-api-first-ticketing-platform) * [What is event-driven architecture in ticketing?](/apis-integrations/what-is-event-driven-architecture-in-ticketing) #### 2 · Headless and embedded delivery * [What is headless ticketing?](/apis-integrations/what-is-headless-ticketing) * [What is embedded ticketing?](/apis-integrations/what-is-embedded-ticketing) * [Hosted vs embedded vs headless ticketing: what is the difference?](/apis-integrations/hosted-vs-embedded-vs-headless-ticketing-what-is-the-difference) * [How can you embed ticketing into an existing website or app?](/apis-integrations/how-to-embed-ticketing-into-a-website-or-app) * [How do you embed a ticketing seat map in an application?](/apis-integrations/how-do-you-embed-a-ticketing-seat-map-in-an-application) * [Can you replace a ticketing backend without rebuilding the frontend?](/apis-integrations/can-you-replace-a-ticketing-backend-without-rebuilding-the-frontend) #### 3 · Building with APIs * [What can developers build with a ticketing API?](/apis-integrations/what-can-developers-build-with-a-ticketing-api) * [How do you build a custom ticketing checkout with APIs?](/apis-integrations/how-to-build-a-custom-ticketing-checkout-with-apis) * [How should ticketing APIs handle authentication, errors and versioning?](/apis-integrations/how-should-ticketing-apis-handle-authentication-errors-and-versioning) * [How do you evaluate a ticketing API and its documentation?](/apis-integrations/how-to-evaluate-a-ticketing-api-and-its-documentation) * [Custom vs prebuilt ticketing integrations: which should you use?](/apis-integrations/custom-vs-prebuilt-ticketing-integrations-which-should-you-use) #### 4 · Enterprise and data integrations * [How do you integrate ticketing into an enterprise technology stack?](/apis-integrations/how-to-integrate-ticketing-into-an-enterprise-technology-stack) * [How do ticketing systems integrate with CRM, ERP and finance software?](/apis-integrations/how-do-ticketing-systems-integrate-with-crm-erp-and-finance-software) * [How does ticketing integrate with membership and loyalty systems?](/apis-integrations/how-does-ticketing-integrate-with-membership-and-loyalty-systems) * [How do ticketing platforms connect to data warehouses?](/apis-integrations/how-do-ticketing-platforms-connect-to-data-warehouses) ## How this subject connects to others #### [Platforms & Infrastructure](/platforms-infrastructure) How much of the experience a business controls decides whether it needs APIs at all. #### [Events & Inventory](/events-inventory) Integrations that show or reserve tickets depend on how inventory is modelled.