Developer documentation

The 4league /v1 API gives your own systems read access to an organization's data: its competitions, teams, players, fixtures and standings. Use it to power a federation portal, a club website or your own reporting. These pages are available in English only.

Server-to-server only. Every request is signed with your key's secret, and /v1 sends no CORS headers. Call it from your own backend, never from a web page or mobile app.

Authentication

Sign each request with HMAC-SHA256: required headers, the canonical string, test vectors and code in Node.js, PHP, Python and cURL.

API reference

Every endpoint with its scope, parameters, errors, pagination, rate limits and example responses.

Federation

A worked example: read an organization tree, list associations and clubs, and fetch standings for each competition.

Versioning

What stays stable within /v1, what counts as a breaking change and how deprecations are announced.

Getting started

  1. Upgrade to PRO. Open your organization in the 4league app. Integrations are managed by its owner and need the PRO plan.
  2. Create a key. Create a signed API key with only the access you need. Keep the secret on your server.
  3. Make your first call. Sign GET https://api.4league.app/v1/ping as shown in Authentication. A successful response confirms your key, its scopes and your server clock.

Base URL

https://api.4league.app/v1

Keys are scoped to one organization. A key sees its own organization and, when created with descendants, everything below it. See the API reference for scopes, limits and errors.