Lucra Sports Tournaments API
Modular tournament management endpoints. Unlike the legacy API which returns everything in a single call,the v2 API separates concerns into dedicated resources:| Resource | Path | Purpose ||----------|------|---------|| **Tournaments** | `/tournaments` | CRUD operations, cancel, complete || **Leaderboard** | `/tournaments/:id/leaderboard` | Paginated participant rankings and scores || **Rewards** | `/tournaments/:id/rewards` | Prize tier configuration and winner assignment |---## Key Differences from Legacy API### Separate ResourcesThe legacy `GET /pool-tournament/:id` returns the tournament, reward structure, and full user leaderboard in one response.The v2 API splits these into three independent endpoints so clients only fetch what they need.### Update and Complete are SeparateThe legacy complete endpoint accepts tournament field updates (title, fee, etc.) in the same request body as the completion action.In v2, update the tournament first via `PATCH /tournaments/:id`, then complete via `POST /tournaments/:id/complete`.### Reward Assignment is ExplicitThe legacy complete endpoint accepts a `paymentStructure` with `userId` to assign winners and complete in one step.In v2, assign rewards first via `PUT /tournaments/:id/rewards`, then complete the tournament separately.---## Tournament Types### CASH_FIXEDPrize pool is defined upfront. Values in the reward tiers represent absolute monetary amounts.### CASH_PERCENTAGEPrize pool is calculated from total entry fees. Values in reward tiers represent percentages that must sum to exactly 100.---## Sign-Up WindowTournaments can optionally define a sign-up window using `signUpStart` and `signUpEnd`.When set, participants can only join during this window. If omitted, sign-ups follow thedefault behavior (open from creation until the tournament expires).| Constraint | Rule ||-----------|------|| `signUpEnd` ≤ `expiresAt` | Sign-ups must close before tournament expiration || `signUpStart` ; rel="next", ; rel="first"```**Available link relations:**| Rel | Description ||-----|-------------|| `next` | Next page of results (omitted on the last page) || `prev` | Previous page of results (omitted on the first page) || `first` | First page of results |**Parsing the Link header:**```typescriptfunction parseLinkHeader(header: string): Record { return Object.fromEntries( header.split(', ').map((part) => { const [url, rel] = part.split('; '); return [ rel.replace('rel="', '').replace('"', ''), url.slice(1, -1), ]; }), );}// Usageconst links = parseLinkHeader(response.headers.link);if (links.next) { // fetch next page}```
Lucra Sports Tournaments API is one of 9 APIs that Lucra Sports publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Tournaments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.
This API exposes 14 operations across 10 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against 3 base URLs: /, https://forge.lucrasports.com, https://forge.sandbox.lucrasports.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Lucra Sports Tournaments API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as X-Lucra-Api-Key (X-Lucra-Api-Key).
X-Lucra-Api-Key— API key for tenant authentication
Paths & Operations 14
Across 10 paths, the API surfaces 14 operations — 4 GET, 3 PATCH, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
Modular tournament management endpoints. Unlike the legacy API which returns everything in a single call, the v2 API separates concerns into dedicated resources: | Resource | Path…
Schemas 21
The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are TournamentUpdateMatchingDto (21 properties), TournamentUpdateDto (20 properties), TournamentCreateDto (20 properties), TournamentResponseDto (20 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Lucra Sports 8
Other APIs Lucra Sports publishes across the network.
This is an independent, third-party profile of Lucra Sports Tournaments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.