APIHorseRacing

Refunds and cancellations

Cancel any time. Tell us if something is wrong.

You are never locked in, and cancelling takes two clicks from your account. Subscriptions are not refunded — but if you think a charge is wrong, there is a form below and a person on the end of it.

Cancelling, and what you keep

Self-serve, immediate, and nothing is cut off early.

01

Cancel from your account

Two clicks in your account. No email, no phone call and no retention maze. Whenever you like.

02

Keep it to the period end

Your plan stays live until the end of the period you have already paid for. You will not be charged again.

03

Your key keeps working

Afterwards it drops to the free plan rather than being switched off, so anything you have built carries on against the delayed window.

The policy

You may cancel at any time and access continues to the end of the current paid period. Except where the law requires otherwise, fees are not refunded and part-used periods are not pro-rated.

Nothing here removes any right you have under consumer law where you live. Where the law gives you more than this policy does, the law wins, and we will not make you argue about it.

Why it works this way

A refund policy is really a statement about how much you can find out before you pay. Here, all of it.

The free key is the trial

It reads the same production database every paid plan reads, on a delayed window. No card, no expiry, no nag screen.

Check the jurisdictions you care about, call the endpoints you intend to use, and satisfy yourself the data does what you need — before anything is charged.

Coverage is counted, not claimed

The coverage page counts every field against every jurisdiction from the archive itself, and /v1/meta/coverage returns the same figures to your code.

The pricing page lists what is not in the archive at all. Nothing about what we hold is a surprise you have to pay to discover.

Usage is recorded

Every request is logged against the key that made it. That is ordinary operations, and it is also the reason we can look at a claim properly rather than guessing.

Someone who called the API twice and found a gap is a different conversation from someone who pulled the archive and then asked for the money back. We treat them differently, and we can tell which is which.

Ask us to look at a charge

We cannot promise a refund — the policy above is the policy — but we would rather hear from you than not. This form is the only way we take these requests, because it opens a ticket with a reference and a thread rather than disappearing into an inbox.

The more specific the better. “The coverage for Ireland was thinner than I expected on going” gets a real answer; “it did not work” gets a question back.

Opens a ticket. We answer oldest first, usually the same working day.