Overview

Ratings for amateur tennis players in Kraków, based on real match results.

KRKplaysTennis API 1.0.1

The KRKplaysTennis API collects singles match results from amateur leagues and tournaments in Kraków and rates each player from those results.

A player’s self-assessed NTRP level sets a starting rating. Each rated match then moves the rating, and a confidence value from 0 to 100 shows how settled the rating is. The rating isn’t an NTRP rating: NTRP is only the starting point.

KRKplaysTennis is a fictional API. All players, venues, competitions, and organizers are invented.

Pagination

List operations return up to limit items in data. When more items exist, next_cursor holds a value to pass as cursor in the next request. When next_cursor is null, you have the last page.

Errors

Errors use RFC 9457 problem details with the application/problem+json media type. Each type URL links to the matching section of the errors reference.

Times

Timestamps follow RFC 3339. Availability windows use local time in the Europe/Warsaw time zone.

KRKplaysTennis docs on GitHub

https://github.com/saveriocirillo/krk-plays-tennis-docs

Information

License: All rights reserved
OpenAPI version: 3.1.0

Authentication

ApiKeyAuth

An API key for every read operation. Send it in the X-API-Key header with each request.

Security scheme type: apiKey

Header parameter name: X-API-Key

ClientBasicAuth

Your OAuth client ID and client secret, sent with HTTP Basic authentication. Only for POST /oauth/token.

Security scheme type: http

OAuth2ClientCredentials

An OAuth 2.0 access token for POST /matches, the only write operation. Competition organizers get tokens with the client credentials flow, and each token expires after 1 hour. Send it in the Authorization header as Bearer <token>.

Security scheme type: oauth2

Flow type: clientCredentials

Token URL: https://auth.krkplaystennis.example/oauth/token

Scopes:

matches:write - Submit match results for competitions you organize.