HZURΛ
HZURA
Interactive Developer Console

Sports Data API Playground

Test HZURA's sports data API. Check health, discover available sports, browse events, inspect odds responses, and generate production-ready integration code.

Request API Access API Documentation
API Playground
Connection: Not tested
Health
Sports
Events
Event + Odds
GET
/api/v1/health

Connectivity check. Verifies the API gateway is alive. Does not require IP allowlisting.

GET

/api/v1/health

Response

Select an endpoint to begin

Choose an endpoint above, configure parameters, then send a request.

Integration Code

curl -sS "https://api.hzura.com/health" \
  -H "Accept: application/json"

How the APIs Connect

From health check to production integration in five steps.

01

Health

Check service availability. Public endpoint, no IP policy required.

02

Sports

Discover which sports are available to the calling IP via GET /sports.

03

Events

Get the event catalog for the selected sport via GET /{sport}/events.

04

Event + Odds

Get one event and its currently available odds via GET /{sport}/events/{eventId}.

05

Integrate

Use the public API URL in your application. Refer to generated code examples.

Quick API Reference

Public API base and documented endpoints.

Full Documentation
Public API Base URL
https://api.hzura.com

All integration requests use this base URL.

Authentication
Server IP Allowlisting

No API keys or Authorization headers. Access is tied to your server's static IP.

Protocol
HTTP GET · JSON Responses

Read-only REST. No query parameters in the current contract.

Documented Endpoints

GET
/api/v1/health
Public

Verifies API gateway availability. Does not require IP allowlisting.

GET
/api/v1/sports
IP Allowlisted

Returns sports available to the calling IP.

GET
/api/v1/{sport}/events
IP Allowlisted

Returns the event catalog for the specified sport.

GET
/api/v1/{sport}/events/{eventId}
IP Allowlisted

Returns one event plus its currently available odds markets.

{sport} comes from the /sports endpoint response (key field).

{eventId} is the gmid from the event list.

Frequently Asked Questions

Common questions about the Sports Data API.

What is HZURA's Sports Data API Playground?

An interactive developer tool for testing HZURA's sports data API. Check health, discover available sports, browse events, inspect event and odds responses, and generate production code.

Why is IP allowlisting used instead of API keys?

IP allowlisting eliminates authorization header overhead and prevents credential compromise. Your server's static public IP is allowlisted, and requests are made directly over HTTPS without any authentication headers.

How do I get event IDs to query odds?

Query GET /api/v1/{sport}/events to get events with their gmid values. Pass the gmid to GET /api/v1/{sport}/events/{eventId} for odds.

Does the API support WebSockets or live streaming?

No. The current API version provides HTTP GET endpoints returning cached data. There is no WebSocket or push feed. Clients should poll events they are interested in and stop polling when events are no longer needed.

Why might I receive a 403 or 429 error?

403 means your calling IP is not allowlisted. 429 means the rate limit was exceeded — honour the Retry-After header before retrying. The /health endpoint is always public.

How do I request production API access?

Contact HZURA with your server's static public IP address. Once allowlisted, your server can query all endpoints directly over standard HTTPS.

Does the API have a separate result endpoint?

No. The current API does not have a separate result endpoint. Event status and outcome data are included in the event response when available.

Ready for Production

Request API Access

Contact HZURA with your server's static IP address to access sports, events, and odds data.

Request API Access Learn MoreAPI Documentation