Front9 Public API
The Front9 Public API lets you read a golf organization's public data — events, players, tee sheets, live leaderboards and odds, season standings, brackets, blog posts, and membership plans — and kick off a few public actions (start a registration or membership purchase, subscribe to a newsletter).
It powers public league sites and embeds, and it's safe to call directly from a browser or a server.
Base URL
All endpoints live under the public base path:
https://api.front9.io/api/public/v1
Replace the host with the environment you're targeting. Every path in the API Reference is relative to this base.
No authentication
Every endpoint in this API is public. There are no API keys, tokens, or cookies — just call it. (Don't send credentials; cross-origin requests are allowed but credential-less. See Authentication.)
A first request
Fetch an organization's upcoming events:
curl "https://api.front9.io/api/public/v1/orgs/{orgSlug}/events?filter=upcoming"
{
"count": 3,
"oldestYear": 2022,
"events": [
{
"id": 42,
"slug": "spring-classic-2026",
"title": "Spring Classic",
"eventType": "tournament",
"status": "published",
"startDate": "2026-04-18T00:00:00Z",
"totalPlayers": 48
}
]
}
{orgSlug} is the organization's URL slug (the same one in its public site URL).
Most endpoints are scoped to an org this way, and events/leaderboards are then
scoped by an event slug.
Conventions at a glance
- JSON in and out (
Content-Type: application/json). - Money is in integer cents — e.g.
registrationFeeMembersCents: 5000is $50.00. - Dates are ISO-8601 / RFC-3339 strings; nullable fields may be
null. - Rate limit: 60 requests/minute per IP — see Rate limits.
- Errors: plain-text body for most failures; JSON for body validation — see Errors.
Where to go next
- Authentication — why there's nothing to configure.
- Rate limits
- Errors
- Pagination
- Real-time updates — live leaderboard & odds via SSE.
- Registration & memberships — the hosted purchase flow.
- API Reference — every endpoint, generated from the OpenAPI spec.