A clean upstream source for FastAPI backends
FastAPI works well when a product needs its own service boundary around external data. Your backend can request the relevant PuntersEdge racing or sports endpoints, apply internal transformations and expose only the response shape your clients need.
This architecture keeps API credentials and integration logic server-side while giving your application control over caching, persistence, derived analytics and access rules. PuntersEdge remains the upstream data source rather than dictating the shape of your own product API.
- Server-side data access
- Backend transformation layer
- Application caching control
- Analytics service inputs
- Client-specific responses
Example API calls
# Swap {sport_key} for a key from /v1/sports
curl "https://api.puntersedge.online/v1/sports/{sport_key}/odds" \
-H "X-API-Key: YOUR_API_KEY"
curl "https://api.puntersedge.online/v1/racing/next-to-go?num_races=5&country=AU" \
-H "X-API-Key: YOUR_API_KEY"