Skip to content

Update a match (v2)

POST/v2/matches/{matchId}

POST
/v2/matches/{matchId}
curl --request POST \
--url https://api.ligr.live/rest/v2/matches/1 \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "name": "example", "venueId": 1, "competitionId": 1, "date": "2026-04-15T12:00:00Z", "competitorsType": "singles", "competitors": [ { "entityId": 1, "entityType": "team", "meta": { "isHome": true } } ], "description": "example", "config": "example", "homeTeamKitKey": "home", "awayTeamKitKey": "home", "homeTeamFormation": "example", "awayTeamFormation": "example" }'

Update an existing match.

matchId
required

Entity identifier

integer format: int32
>= 1

The match properties to update

Media typeapplication/json
object
name

Match name

string
>= 5 characters <= 42 characters
venueId

Entity identifier

integer format: int32
>= 1
competitionId

Entity identifier

integer format: int32
>= 1
date
string format: date-time
competitorsType

The match format: singles, doubles, teams or group. It is one value for the match. Each row in competitors has its own entityType. For example, a doubles match has competitorsType: doubles and four entityType: player rows. A group match has player rows.

string
Allowed values: singles doubles teams group
competitors
Array<object>
object
entityId
required

Entity identifier

integer format: int32
>= 1
entityType
required

The kind of one competitor row: team or player. A teams match has team rows. A singles, doubles or group match has player rows.

string
Allowed values: team player
meta
object
isHome
required
boolean
description

Free text about the match.

string
config

Match rules for this match only. The value applies onto the stored match config, or onto the competition matchConfig when the match has none: a key that you omit keeps its value. Nested objects, arrays and null work as on POST /v2/matches. The API checks rules and, for tennis, the scoring. A value that fails the check returns 400 with the reason, and nothing changes. LIGR then rebuilds the match summary from its facts with the new rules.

homeTeamKitKey
string
Allowed values: home away alt alt2
awayTeamKitKey
string
Allowed values: home away alt alt2
homeTeamFormation

Football only. The formation of the home team as an Opta code without dashes, for example 442, 433 or 4231. Send null to remove it.

string
nullable
awayTeamFormation

Football only. The formation of the away team as an Opta code without dashes, for example 442, 433 or 4231. Send null to remove it.

string
nullable

No content

Request is invalid

Media typeapplication/json
object
message
required
string
details
required
object
key
additional properties
Examplegenerated
{
"message": "example",
"details": {
"additionalProperty": "example"
}
}

Missing or invalid api key

Media typeapplication/json
object
message
required
string
Examplegenerated
{
"message": "example"
}

Api key provides insufficient access for the request

Media typeapplication/json
object
message
required
string
Examplegenerated
{
"message": "example"
}

Match not found

Media typeapplication/json
object
message
required
string
Examplegenerated
{
"message": "example"
}

Organization has made too many requests

Media typeapplication/json
object
message
required
string
Examplegenerated
{
"message": "example"
}

An unexpected error has occured. If problems persist please contact support

Media typeapplication/json
object
message
required
string
Examplegenerated
{
"message": "example"
}