API Keys and Integrations
Live Tourney offers a private API key that approved integration partners can use to read your event data on your behalf. This guide covers generating your key, the available built-in integrations, and how partner access works.
Built-In Integrations
The Integrations tab in Settings includes the following built-in integrations:
| Integration | Purpose |
|---|---|
| API Key | Generate a private key for partner integrations |
| Stripe | Connect a payout account for tournament collections |
| Lightspeed Golf | Sync members from your Lightspeed Golf organization |
| Lightspeed Retail | Available once your Lightspeed Golf organization is connected |
Your API Key
Each Live Tourney user has a single private API key. There is no naming, no per-key permissions, and no list view — just one key on your account at a time.
Generate Your Key
- Go to Settings
- Click the Integrations tab
- Find the API Key section at the top
- Click Generate API Key
- Use Show/Hide to reveal the key, then Copy to copy it to your clipboard
Generating a new key replaces any existing key, so be sure to update any application using the old value.
Delete Your Key
Click Delete API Key in the API Key section to revoke the key immediately. Any application using the deleted key will stop working.
API Access
The Live Tourney v1 API is currently partner-only. Calling the API requires two pieces:
- Your user API key (generated in Settings, above)
- A partner API key issued by Live Tourney to approved integration partners
If you have built an application you would like to connect to Live Tourney, contact help@livetourney.com to discuss partner access.
Authentication
Every request sends both keys as HTTP headers:
Authorization: Bearer <your-key-from-settings>
X-Partner-Key: <partner-key-issued-by-live-tourney>
Requests without both headers are rejected with a 401. Repeated failed attempts from one address are slowed down with a 429.
Available Endpoints
| Endpoint | Function |
|---|---|
GET /api/v1/account |
Confirms both keys are valid and returns the club's name and email |
GET /api/v1/events?date=YYYY-MM-DD |
Lists each playable round on that date. Use from and to instead of date for a range of up to 31 days |
GET /api/v1/events/{eventId} |
One event by its ID from the list above |
GET /api/v1/events/{eventId}/pairings |
The tee sheet (groups and players) for an event |
GET /api/v1/events/{eventId}/payouts |
Each player's computed winnings for that round once you have saved its payouts, for partners that credit player accounts. A league week returns that week's money; the league itself returns the season prizes |
GET /api/v1/events/{eventId}/scores |
Live and final scores for a stroke-play event: each entry's gross and net totals, to-par, holes played, leaderboard position, handicaps, and hole-by-hole scores. A multi-round round returns that round; the multi-round event itself returns cumulative standings plus every round |
GET /api/v1/events/{eventId}/payments |
Every online registration payment and refund for an event: who paid, the players it covered, what it covered (entry fees, add-ons, processing fee), the amount, card fees and net. Offline payments you marked paid by hand are not included. Use the after cursor from each response to pick up only new payments |
The full request and response reference, including every field, is published at livetourney.com/api-docs.
Common Errors
Every error is returned as { "error": { "code": "...", "message": "..." } }.
| Status and code | Meaning |
|---|---|
401 invalid_partner_key |
X-Partner-Key header is missing or unrecognized |
401 invalid_club_key |
Authorization: Bearer key is missing or does not match a user |
404 event_not_found |
The event ID is unknown or belongs to a different account |
400 unsupported_event_type |
/scores was called for a match-play event (Ryder Cup, league, or bracket), which has no gross or net totals to report |
422 invalid_request |
Missing or invalid date, from, or to on /api/v1/events, or an invalid after or limit on /payments |
429 rate_limited |
Too many requests; wait for the number of seconds in the Retry-After header |
API Key Security
Your API key authenticates requests on your behalf. Treat it like a password.
| Practice | Why |
|---|---|
| Keep it secret | Never share publicly or paste in screenshots |
| Use environment variables | Don't hardcode keys into your application |
| Avoid client-side use | Anything in browser/mobile-app code is visible to users |
| Don't commit to source control | Keys in public repos are scraped within minutes |
If you believe your key has been exposed, delete it from Settings, generate a new one, and update any application that was using it.