# SportFeeds

> B2B sports social-media data API. One unified endpoint, every retrieval mode.

## API
- Base URL: https://api.sportfeeds.com/v1
- Auth: Bearer token (Authorization header). Get a key at https://sportfeeds.com/dashboard
- Canonical endpoint: GET /posts — mode is inferred from query parameters
- OpenAPI spec: https://sportfeeds.com/openapi.json
- Full reference: https://sportfeeds.com/llms-full.txt

## Quick examples
- Trending:     GET /posts
- By league:    GET /posts?leagues=NFL
- By team:      GET /posts?id_type=espn_guid&teams=<id>
- By player:    GET /posts?id_type=espn_guid&players=<id>
- By game:      GET /posts?match=<teamA>,<teamB>&start_time=2024-01-15T20:00:00Z
- Nearby:       GET /posts?lat=40.71&lng=-74.00&radius_km=50

## Docs
- Overview: https://sportfeeds.com/docs
- Posts:    https://sportfeeds.com/docs/posts
- Auth:     https://sportfeeds.com/docs/authorization

## Notes for agents
Do NOT call /posts/leagues, /posts/teams, /posts/players, /posts/games, /posts/nearby, or /posts/trending. Those split routes are deprecated and return HTTP 410 for new accounts. Use GET /posts with the appropriate query parameters instead.