How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.

14 operations 10 paths 21 schemas 4 GET3 PATCH5 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://forge.lucrasports.com
Authentication
API Key
Resource Areas
1

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.

Tournaments 14

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…

POST
/api/tournaments
Create Tournament
TournamentsApiController_createTournament body → 201
GET
/api/tournaments
List Tournaments
TournamentsApiController_getTournaments 4 params → 200
PATCH
/api/tournaments
Update Tournament by Metadata
TournamentsApiController_updateMatchingTournament body → 200
POST
/api/tournaments/complete
Complete Tournament by Metadata
TournamentsApiController_completeMatchingTournament body → 202
PATCH
/api/tournaments/{id}
Update Tournament
TournamentsApiController_updateTournament 1 param body → 200404
GET
/api/tournaments/{id}
Get Tournament
TournamentsApiController_getTournament 1 param → 200404
POST
/api/tournaments/{id}/cancel
Cancel Tournament
TournamentsApiController_cancelTournament 1 param → 200404
POST
/api/tournaments/{id}/complete
Complete Tournament
TournamentsApiController_completeTournament 1 param body → 404
POST
/api/tournaments/scores
Ingest Scores
TournamentsApiController_ingestScores body → 202
PUT
/api/tournaments/{id}/tags
Set the tags assigned to a tournament.
TournamentsApiController_setTournamentTags 1 param body → 200404
GET
/api/tournaments/{id}/leaderboard
Get Tournament Leaderboard
TournamentLeaderboardController_getTournamentLeaderboard 3 params → 200404
PATCH
/api/tournaments/rewards
Update Tournament Rewards by Metadata
TournamentRewardsController_updateMatching body → 200404
PUT
/api/tournaments/{id}/rewards
Update Tournament Rewards
TournamentRewardsController_updateTournamentRewards 1 param body → 200404
GET
/api/tournaments/{id}/rewards
Get Tournament Rewards
TournamentRewardsController_getTournamentRewards 1 param → 200404

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.

CompleteMatchingPaymentRowDto
object
5 properties 2 required
TournamentRewardsUpdateDto
object
1 property 1 required
TournamentRewardTierUpdateDto
object
6 properties 1 required
IngestUserScoreDto
object
5 properties 1 required
NewRewardDto
object
8 properties 3 required
TournamentIdentifierDto
object
4 properties
TournamentTagsResponseDto
object
1 property 1 required
TournamentUpdateMatchingDto
object
21 properties 1 required
TournamentCompleteMatchingDto
object
2 properties 1 required
SetTournamentTagsDto
object
1 property 1 required
TournamentUpdateDto
object
20 properties
TournamentLeaderboardEntryResponseDto
object
8 properties 8 required
TournamentRewardResponseDto
object
6 properties 6 required
Error
object
3 properties 3 required
IngestUserScoreEntryDto
object
6 properties 1 required
TournamentRewardTierUpdateMatchingDto
object
8 properties 1 required
TournamentCompleteDto
object
1 property
TournamentResponseDto
object
20 properties 20 required
TournamentCreateDto
object
20 properties 3 required
PaymentStructureRowDto
object
3 properties
TournamentRewardsUpdateMatchingDto
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lucra-sports-tournaments-api-openapi.yml Raw ↑

Other APIs Lucra Sports publishes across the network.

Lucra Sports Health API
Lucra Sports Locations API
Lucra Sports Recreational Games API
Lucra Sports States API
Lucra Sports Tenant Tag Groups API
Lucra Sports Tournaments (Legacy) API
Lucra Sports User Score API
Lucra Sports Webhooks API
Where this information came from

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.