Skip to main content

AnglerPass API · v1

Build on AnglerPass

The infrastructure layer for private fishing access. Property discovery, guide management, club operations, fly-shop integrations, AI trip planning, and mobile apps — all on one versioned, secure API.

One request away

Clean, predictable, versioned

Every response uses the same envelope and carries a request ID. JSON only. Built to be consumed by apps, agents, and large language models alike.

bash
GET /v1/properties?state=CO&species=trout
response
{
  "success": true,
  "data": { "properties": [ { "name": "Upper Roaring Fork — Beat 3",
    "state": "CO", "water_type": "river",
    "species": ["Rainbow Trout", "Brown Trout"],
    "coordinates_precision": "approximate" } ] },
  "meta": { "request_id": "req_9f2c1a7b", "pagination": { "total": 42, "has_more": true } }
}

What you can build

A platform, not just an endpoint

Property search

Discover published private waters by state, species, water type, and map bounds — with privacy-safe coordinates.

Guide search

Live, background-checked guides ranked Pro-first, filterable by species, technique, and rating.

Club & fly-shop directories

Active clubs and live fly-shop partners for tourism boards and destination marketing.

Availability

Public availability calendars for booking widgets and trip planners.

AI trip planning

Structured, LLM-friendly responses purpose-built for agents and assistants.

Mobile & marketplace

One consistent, versioned API behind iOS, Android, and marketplace integrations.

Who builds on it

Example integrations

Fly ShopsLodges & ResortsGuides & OutfittersTourism BoardsDestination MarketingState Wildlife AgenciesMobile AppsTravel PlatformsAI AssistantsLarge Language ModelsOutdoor BrandsTerritory Holdings platforms

Security & privacy

Private water, protected by design

The promises AnglerPass makes to landowners, members, and conservation partners are enforced at the API boundary — not left to callers.

  • Exact GPS, gate codes, and access notes are never returned — coordinates are approximate.
  • Landowner identities, lease terms, and financials stay private.
  • Club member rosters and member PII are never exposed.
  • Bookings, payments, and payouts are out of scope for the public API.
  • Conservation-sensitive locations are protected at the boundary.
Read the security model

Partner program

Request API access

The API is currently available by application. Tell us what you're building and our partnerships team will follow up with a key and next steps.

Already have access? Head to the developer portal.