A person reads
every ticket.

Sign in with Google and one is issued immediately. No card, no sales call, no waiting for approval.

Nine of the forty endpoints, on results at least seven days old: players, competitions, the calendar, finished matches, head to head and coverage. Sixty calls a minute and five hundred a day, which is enough to build something real before deciding whether to pay.

https://api.dartsapi.com/v1. Every answer is JSON, and https://api.dartsapi.com/ answers without a key if you only want to check you can reach it.

As an Authorization: Bearer da_live_… header. Not a query string, because those end up in logs, proxies and screenshots.

The free key is the sandbox. Same archive, same response shapes, just delayed, so nothing you build against it behaves differently when you upgrade.

The endpoint exists, your plan does not reach it. Every refusal names the plan it needs and links to pricing, rather than a bare status leaving you guessing.

Moving up takes effect immediately and the difference goes on your next invoice. Moving down also applies immediately, with the unused part credited against the next invoice. Both are in Manage billing.

From your dashboard. The old key stops the moment the new one is issued, so change it in your code first. Rotation needs the confirmation box ticked, because there is no undo.

One key per account today, which you can rotate from your dashboard at any moment. Separate staging and production keys are coming to paid plans, and usage stays counted per account, so a second key never means a second allowance.

Access continues to the end of the period you have paid for, then the same key drops to free-plan reach rather than dying. Your integration degrades instead of breaking.

Not automatically, and we say so on the refunds page rather than burying it. Cancel any time and keep access to the end of the period. If a charge looks wrong, the form on that page opens a review and a person answers it.

Never. A call past your limit gets a 429 with Retry-After and a sentence saying when to come back, and there is no overage bill. Calls we refuse for plan or parameters never count against you either.

Card, through Stripe. We never see or store your card details.

Yes. Annual is twelve months at ten months’ price on every paid plan.

Add it in Manage billing and it appears on every invoice from then on. Stripe holds the billing details, so you edit them there rather than asking us.

Manage billing in your dashboard, one click, no notice period and nothing to send us. Your dashboard then shows the date access runs to.

To 2000. It currently holds more than 115,000 matches across 2,900 events and 11,800 players, and it is still filling as older seasons are read in.

Published results and statistics, compiled and checked by us, plus our own calculations on top of them. We do not republish anyone else’s feed.

The archive is checked for new results every few minutes and updates as they are published. Every response carries data_as_of, so you always know how old an answer is. The free key sees results once they are seven days old.

Because we do not hold it, and inventing a value would be worse. Coverage varies by era: a 2003 televised final carries far more detail than a 2003 qualifier.

Yes. Youth darts is covered in depth, with 309 Junior Darts Corporation events held, and women’s events are held wherever their results are published. Every player follows the same rule: results and averages from the first match, and the full set of statistics once they reach 25 matches or play a major. /v1/coverage gives the measured figures by season.

No. Bulk export is not offered. /v1/matches with a cursor walks the whole set as fast as you can consume it.

That is correct. Ids carry their type, so a player id passed where a match belongs fails loudly instead of quietly returning the wrong thing. Raw integers are refused.

page for a UI pager, cursor for walking the whole set. A cursor pages by sort position, so page 10,000 is as fast as page 1 and a new match arriving cannot shift the boundary under you.

Not yet. An OpenAPI spec, a Postman collection and an MCP server are being built, all generated from the one registry that runs the API itself, so none of them can drift from what the endpoints actually do. Until then, the endpoint pages on this site give every parameter and response shape.

Free key: 60 a minute and 500 a day. Live and Archive: 120 a minute and 250,000 a month. Complete: 180 a minute and 600,000 a month. Analyst: 240 a minute and 1,000,000 a month. Every response tells you where you stand in X-RateLimit-Remaining for the minute and X-Allowance-Remaining for the day or month, and /v1/usage gives the full picture.

No. Stable ids are a promise in the terms, not an implementation detail. A rebuild maps everything back to the same ids.

It carries every match in play with the score as it stands and each player’s average, refreshed every five minutes. Every response states when it was taken in captured_at and how old that is in age_seconds, so a score can be a few minutes behind the board but never passes for newer than it is. If the feed falls more than twenty minutes behind, the response says so. Live is on paid plans.

Not switched on, and we say so plainly rather than listing an endpoint that does not answer. The change feed and webhooks cover the same ground without a socket to keep alive.

Stripe-shaped, deliberately: t=<unix>,v1=<hmac>, so verification code you already have works unchanged.

Delivery retries with backoff over about three days. Repeated failures disable the endpoint and write it to your activity log, so it fails loudly rather than silently.

Yes, on the free key. /v1/fixtures lists the whole published draw of each tournament under way, not just the next few matches, filtered by date, competition or player. A date the organiser has fixed is marked confirmed, and one not yet fixed is marked unconfirmed rather than guessed. Players carry the same ids as everywhere else, and a qualifier the archive does not yet know is named with no id.