PickleStats API

Pickleball facilities & courts data,
one API call away

Locations for ~4,900 facilities and ~17,800 courts across all 50 US states — with lat/lng coordinates, surface, lighting, access, and provenance. Clean REST, JSON, built for developers.

Get an API keyRead the docs
api.picklestats.app
GET /v1/facilities?near=33.61,-117.87

200 OK

{
  "data": [
    {
      "id": "fac_x7k2m9qp4d1z",
      "name": "Laguna Niguel Pickleball Courts",
      "state": "CA",
      "court_count": 12,
      "surface": "concrete",
      "lit": true,
      "distance_km": 3.42
    }
  ],
  "meta": { "total": 37 }
}

Pricing

Cancel anytime.

Starter

$19/mo
  • 10,000 requests / month
  • 60 requests / minute
  • Full facilities & courts data
Subscribe

Pro

$49/mo
  • 100,000 requests / month
  • 300 requests / minute
  • Full facilities & courts data
Subscribe

Scale

$149/mo
  • 1,000,000 requests / month
  • 1,000 requests / minute
  • Full facilities & courts data
Subscribe

Frequently asked questions

What data does the PickleStats API provide?

Roughly 4,900 pickleball facilities and 17,800 courts across all 50 US states, each with location coordinates, court counts, surface type, lighting, indoor/outdoor status, access details, and data provenance.

Can I use this as a pickleball locations API?

Yes — every facility record includes latitude/longitude coordinates plus city and state, so PickleStats works as a pickleball locations API for maps, court finders, and directories. Query locations by proximity, state, or free-text search.

How do I find pickleball courts near a location?

Call GET /v1/facilities with a near=lat,lng parameter and an optional radius_km. You can also filter by state, surface, lighting, indoor/outdoor, minimum court count, or free-text search.

Is there a free tier?

No — the API is a paid subscription starting at $19/month for 10,000 requests. All plans include the full facilities and courts dataset and can be canceled anytime.

How is the API authenticated?

With a bearer API key. Create an account, subscribe to a plan, and generate a key from the dashboard, then send it as an Authorization: Bearer header.

What format are responses in?

Clean JSON over REST. The full OpenAPI 3.1 specification is public, and interactive documentation is available at /docs.