ForHosting KIT · Developer Utilities

Tennis tiebreak score calculator

A tennis set that reaches six games all is decided by a tiebreak, not another service game.

● BetaFree · in your browser

Use it from WebAPIEmailTelegramApp soon

Each player’s points tell you more than the scoreboard headline: whether the breaker is still live, who must hold serve next, and whether someone has already closed it out under the win-by-two rule. Coaches, umpires, streaming overlays, and league apps need that state from two integers without standing up a full match engine. This tennis tiebreak score calculator accepts each player’s points, who served the first point, and whether the breaker is a seven-point set tiebreak or a ten-point match tiebreak. It returns a deterministic board state: the printed score, whether the tiebreak is won, who serves the next point, whether the ends change, and how many points each player still needs. The same pure arithmetic runs in the free browser widget and on the API path, so a court-side helper and a backend scorer never disagree on seven–five versus eight–six.

How to use it

Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.

Check your inputs

Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.

Use it again or automate it

Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.

What you can do with it

Get an answer now

Enter one set of values and see the result without building a spreadsheet or script.

Compare scenarios

Change one value at a time and rerun the calculation to understand what affects the result.

Automate repeated work

Use the API when the same calculation needs to run inside your product or workflow.

FAQ

How do I use this capability?

Complete the fields above and run it on this page. The form highlights anything that needs attention.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/hobby/sport-tennis-tiebreak

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/hobby/sport-tennis-tiebreak \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"points_a":6,"points_b":5}'

const res = await fetch("https://api.kit.forhosting.com/hobby/sport-tennis-tiebreak", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "points_a": 6,
    "points_b": 5
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/hobby/sport-tennis-tiebreak",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "points_a": 6,
    "points_b": 5
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/hobby/sport-tennis-tiebreak", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"points_a":6,"points_b":5}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"points_a":6,"points_b":5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/hobby/sport-tennis-tiebreak", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "points_a": 6,
  "points_b": 5
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "hobby.sport_tennis_tiebreak",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →