Competier
  1. result
Competier
  • api-key
    • Creates and returns a new api key, invalidating the previous one.
      POST
  • ladder
    • Adds a ladder to an account.
      POST
    • Deletes a ladder from an account, including all its entries, ratings and results.
      DELETE
    • Gets ladders of an account.
      GET
  • ladder-entry
    • Adds a self-managed entry to a ladder.
      POST
    • Deletes a ladder-entry from a ladder, including all its ratings and results.
      DELETE
    • Gets ladder entries.
      GET
  • result
    • Adds a game result for a played game.
      POST
    • Deletes a game result by rolling it back, reverting rating changes.
      DELETE
    • Gets game results.
      GET
  • invite
    • Adds an invite.
      POST
    • Accepts an invite.
      PUT
    • Deletes an invite.
      DELETE
    • Gets invites.
      GET
  • account
    • Updates account data.
      PATCH
  • credit
    • Fetches credit info.
      GET
  • matchmaking
  • bulk
  1. result

Adds a game result for a played game.

POST
/v1/result
Adds a game result for a played game, triggering rating calculation.
It's possible to enter more than two participants, as shown in the example. The Glicko/Elo algorithms don't originally support this - our implementations treat it as 'every entry playing a game against all other entries' and then scale down the total results according to the amount of entries in order to prevent overinflated rating/deviation changes. Due to it being less likely to score your mathematically expected result in a field of, let's say, 20 entries vs. a field of only 2 entries, in practice, rating changes will be slightly less pronounced in larger fields on average. If your type of game/sport/competition lends itself to very large fields, you should consider employing a minimum amount of entries that has to be reached for results to count.

Request

Authorization
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
Body Params application/json

Example
{
    "ladderId": 0,
    "tournamentId": 0,
    "ladderEntryIds": [
        123,
        42,
        13,
        7
    ],
    "entryTeams": [
        1,
        3,
        2,
        2
    ],
    "finishPositions": [
        1,
        2,
        3,
        3
    ],
    "data": ""
}

Request Code Samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://api.competier.net/v1/result' \
--header 'Content-Type: application/json' \
--data-raw '{
    "ladderId": 0,
    "tournamentId": 0,
    "ladderEntryIds": [
        123,
        42,
        13,
        7
    ],
    "entryTeams": [
        1,
        3,
        2,
        2
    ],
    "finishPositions": [
        1,
        2,
        3,
        3
    ],
    "data": ""
}'

Responses

🟢200OK
application/json
Body

Example
{
    "id": 0,
    "ladderId": 0,
    "tournamentId": 0,
    "ladderEntryIds": [
        123,
        42,
        13,
        7
    ],
    "entryNames": [
        "Alice",
        "Bob",
        "Charlie",
        "Dave"
    ],
    "entryTeams": [
        1,
        3,
        2,
        2
    ],
    "finishPositions": [
        1,
        2,
        3,
        3
    ],
    "oldRatings": [
        1500,
        1500,
        1500,
        1800
    ],
    "ratingChanges": [
        29,
        3,
        -12,
        -20
    ],
    "reliabilityDeviationChanges": [
        123,
        123,
        123,
        123
    ],
    "volatilityChanges": [
        0
    ],
    "data": ""
}
🟠400Bad request
🟠401Unauthorized
🟠429Too Many Requests
Modified at 2025-01-04 19:37:12
Previous
Gets ladder entries.
Next
Deletes a game result by rolling it back, reverting rating changes.
Built with