Ways to integrate

Hosted, Embedded / SDK,
or API.

Every product is offered in the same three ways. They all end with the same booking in the same database — what changes is who renders the pixels and whose domain the visitor is on. Here is one camp listing, built all three ways.

Your markup, your styling Rendered by The Good Game

Hosted — the whole page is ours

You put a link in your nav. The visitor leaves your site and lands on our page. You write no code and own no UI.

my-v2.thegoodgame.com/s/org/…
Everything is outlined — the header, the filters, the cards, the buttons. Your logo is on it, but it's our page on our domain.

You write: one <a href>. · SEO credit: our domain.

Embedded / SDK — our components inside your page

You load one script and keep your own site. Our UI renders inside it — as injected event cards, and as a checkout that opens over the top. The visitor never leaves your domain.

https://riversidesports.com/camps
Your header, your hero, your filter form. Only the card grid is outlined — that block of HTML came from us and was injected into your page.
Direct single-camp checkout 
<script src="https://my-v2.thegoodgame.com/embed.js" defer></script>
<button data-tgg-checkout data-event-id="{event_id}">Register</button>

You write: your page + a script tag. · SEO credit: your domain.

The SDK supports two checkout options

Single-camp checkout (default): a Register button opens checkout directly for one camp.

Multi-camp checkout (optional): buyers add several camps from your organization to a cart and pay once, with one charge. Customize the widget’s colors, placement and labels.

Your TGG contact switches Multi-Camp Cart on or off for your organization in TGG admin; this choice is not a code flag. The existing loader shows the enabled cart without a partner deploy. Compare both options visually · Cart buttons and API.

API — you render every pixel

You call us for JSON and build the page yourself, in your own framework and design system. Nothing of ours appears on screen.

https://riversidesports.com/camps
Nothing is outlined. The events, prices and availability came from our API; every pixel is yours — four columns instead of three, your own card design.
cURL — no key, no auth 
curl "{API_BASE_URL}/api/v1/organizations/{organization_id}/events?size=20"

You write: everything the user sees. · SEO credit: your domain.

Side by side

  Hosted Embedded / SDK API
Who renders the page Us You, with our components inside You
Whose domain Ours Yours Yours
You write A link A script tag Your whole front end
SEO credit Our domain Your domain Your domain
Rough estimate Under an hour Half a day A sprint
Ever in the payment path? No No No — checkout still runs through the SDK

Estimates are ours, for a developer already comfortable with the stack — not measured across live integrations.

You choose per product, not once

These aren't tiers. Taking our checkout as an embed while driving staffing purely by API is a completely normal shape — and the most common one is API for listings plus the SDK for the transaction, so you own discovery without ever touching card data.

Next

Keep going

See it
Product tour

A demo of everything we offer, and which of the three ways each one supports.
Decide
Example integrations

Four businesses, and the very different mixes each one takes.

Ready to build?

Getting started tells you exactly what to ask us for — and there's a copy-paste email at the bottom of it. Or just write to us: an organization ID, an API key, a staging event to test against, or something still marked Preview or Planned.

Contact us