← Back to all docs

EZLinks API

EZLinks (now part of GolfNow for Business) is a golf course management and tee time reservation platform powering tee sheets, point of sale, payments, and marketing for golf facilities. An unofficial API lets you programmatically pull tee times, reservations, golfer and member records, POS transactions, payments, and rate/pricing data—and push updates like new bookings, check-ins, and rate changes back into the platform.

By Alex KlarfeldMay 30, 2026
EZLinks API

What is EZLinks?

EZLinks is a golf course management and tee time reservation platform, now part of GolfNow for Business. Golf facilities use it to manage tee sheets and reservations, run point of sale across pro shops and restaurants, process online, phone, on-course and in-store payments, distribute tee times to a marketplace of active golfers, and drive revenue with dynamic pricing and marketing tools—delivered through cloud software that powers more course operations than any other platform.

Core product areas include:

  • Tee Sheet & Reservations (manage tee times, capture golfer information, prevent double-bookings)
  • GN Pro cloud operations software for end-to-end course control
  • Point of Sale for pro shops and restaurants with mobile check-in and ordering
  • Payment processing for online, phone, on-course, and in-store transactions
  • Marketing command center, dynamic/smart pricing, and the tee time marketplace
  • GN Premier membership and club management plus business intelligence reporting

Common data entities:

  • Tee Times, Reservations, Bookings, Confirmation Numbers
  • Golfers, Members, Customer Profiles, Loyalty Accounts
  • POS Transactions, Orders, Inventory, Products
  • Payments, Refunds, Settlements
  • Rates, Pricing Rules, Specials, Promotions
  • Courses, Facilities, Tee Sheets, Reporting Metrics

The EZLinks Integration Challenge

Golf operators run daily reservations, retail, and payments on EZLinks, but turning its portal- and terminal-driven workflows into API-driven automation is non-trivial:

  • No public developer API: tee sheet, POS, and payment data live behind authenticated operator portals and terminals rather than documented endpoints
  • Real-time inventory sensitivity: tee times change second-by-second, so integrations must read and write without creating double-bookings
  • Marketplace distribution gates: inventory is shared into the GolfNow marketplace, and partner access typically requires agreements before data flows
  • Per-facility configuration: pricing rules, rate cards, and tee sheet layouts are tailored per course, so generic integrations break across facilities
  • Authentication complexity: operator logins and session handling complicate headless automation
  • Payment and POS reconciliation: transactions span online, phone, on-course, and in-store channels that must be matched back to bookings and golfers

How Supergood Creates EZLinks APIs

Supergood reverse-engineers EZLinks' authenticated operator flows to deliver a resilient API layer for your facilities—across tee sheet, reservations, POS, payments, and rate management.

  • Handles operator login and session management securely
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across tee times, golfers, POS transactions, payments, and rates so you integrate once and rely on consistent objects
  • Aligns with per-facility pricing rules, tee sheet layouts, and entitlements to ensure correct, conflict-free writes

Use EZLinks with AI agents: EZLinks MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your facilities, modules, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready EZLinks adapter tailored to your facility configuration and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as EZLinks evolves.

ezlinks

API Endpoints

Authentication

POST/authenticate

Authenticate to an EZLinks operator account and obtain a session token for downstream calls.

Reservations

GET/tee_times

List available and booked tee times across courses with filters for date, facility, and rate.

Reservations

POST/create_reservation

Book a tee time against a course and rate, returning a confirmation number while preventing double-bookings.

Customers

GET/golfers

Retrieve golfer and member profiles, loyalty accounts, and booking history.

Point of Sale

GET/transactions

Pull POS transactions, orders, and inventory activity across pro shop and restaurant channels.

Payments

GET/payments

List payments, refunds, and settlements across online, phone, on-course, and in-store channels.

Use Cases

Sync tee times and reservations into your stack

- Pull real-time tee time availability and bookings across all your facilities into a single system - Push new reservations and cancellations back to EZLinks without double-bookings - Stream confirmation numbers and check-in status to downstream apps and notifications

Unify golfer and member data

- Sync golfer profiles, member records, and loyalty accounts into your CRM or warehouse - Reconcile booking history against customer 360 for marketing and retention - Trigger campaigns when a golfer books, cancels, or hits a loyalty threshold

Reconcile POS transactions and payments

- Pull POS orders and inventory activity from pro shop and restaurant channels into accounting systems - Match payments, refunds, and settlements across online, phone, on-course, and in-store channels - Surface daily revenue and round metrics to business intelligence dashboards

Automate rate and pricing management

- Read rate cards, specials, and dynamic pricing rules per facility - Push pricing and promotion updates back into the tee sheet - Align marketplace inventory placement with your revenue strategy

Technical Specifications

Authentication

Operator login and session handling managed in a secure, automated session

Connectivity

Authenticated operator portal flows reverse-engineered into a stable API surface

Response format

Normalized JSON across tee times, golfers, POS transactions, payments, and rates

Rate limits

Adaptive throttling tuned to your facilities to avoid platform-side limits

Session management

Automatic session refresh, re-authentication, and credential rotation

Data freshness

Near real-time pulls for tee times, reservations, and payments with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for new bookings, cancellations, check-ins, and payment events

Latency

Sub-second reads on cached entities; multi-second writes when posting reservations and POS transactions

Throughput

Horizontally scaled workers sized to multi-facility tee time and transaction volume

Reliability

Retry, backoff, and idempotency keys for reservations, payments, and rate changes to prevent double-bookings

Adaptation

Continuous monitoring of EZLinks and GolfNow for Business releases and per-facility configuration drift

Frequently asked questions

EZLinks does not publish a general-purpose developer API; tee sheet, POS, and payment data live behind authenticated operator portals. Supergood builds a resilient API layer against those authenticated surfaces so you can integrate without one.

Yes. Supergood reads real-time availability and uses idempotency keys and conflict-aware writes when creating reservations, so concurrent bookings do not collide on the same tee time.

Yes. EZLinks operations now run under GolfNow for Business (GN Pro and related products). Supergood adapts to the current authenticated surfaces and tracks releases as the platform evolves.

Yes. Each facility is profiled against its own tee sheet layout, rate cards, and pricing rules, and Supergood normalizes the data so multi-facility operators integrate once across all courses.

Supergood normalizes POS transactions and payments across online, phone, on-course, and in-store channels and matches them back to bookings and golfers for clean reconciliation.

Ready to get a real API?