How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Betfair Heartbeat API

HeartbeatAPING - dead man's switch that cancels unmatched bets.

Betfair Heartbeat API is one of 7 APIs that Betfair publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Heartbeat. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 1 operation across 1 path, and defines 1 schema. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, https://api.betfair.com/exchange.

1 operations 1 paths 1 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.betfair.com/exchange/betting
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Betfair Heartbeat API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Application (appKey). An API key is passed in the header as X-Authentication (sessionToken). By default, every request must be authenticated.

  • appKey — The developer Application Key (delayed or live).
  • sessionToken — The session token (ssoid) obtained from identity SSO login.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Heartbeat 1

HeartbeatAPING - dead man's switch that cancels unmatched bets.

POST
/heartbeat/rest/v1.0/heartbeat/
Heartbeat (dead man's switch)
heartbeat body → 200default

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ApiError (3 properties). Each schema is shown below with its type and property counts.

ApiError
object
Betfair APINGException / AccountAPINGException envelope. In JSON-RPC the error is returned under the JSON-RPC "error" member; in REST it is the HTTP 400 body.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

betfair-heartbeat-api-openapi.yml Raw ↑

Other APIs Betfair publishes across the network.

Betfair Exchange Stream API
Betfair Vendor API
Betfair Accounts API
Betfair Betting API
Betfair Historic Data API
Betfair Identity API
Where this information came from

This is an independent, third-party profile of Betfair Heartbeat API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.