Registrations

GET /tournaments/{tournament_id}/registrations

Authorized Access

Returns the registrations of the given tournament.

Resource URL

https://api.toornament.com/organizer/v2/tournaments/{tournament_id}/registrations

HTTP headers

  • X-Api-Key
    string

    API key of your application (see Authentication)

  • Authorization
    string

    Access token with organizer:registration scope (see Authorization)

  • Range
    string

    A range of requested items using the registrations unit. The size of the range cannot exceed 50. (see Pagination)

    Example: registrations=0-49

Query Parameters

  • sort
    string

    A method to sort the filtered data. created_asc and created_desc sorts using the date the registration was added.

    Possible values: created_asc, created_desc

    Default: created_asc

Request Body

This endpoint doesn't require a request body.

Response

[206] Registrations retrieved

Example
[
    {
        "id": "375143143408309123",
        "tournament_id": "378426939508809728",
        "participant_id": "375143143408309123",
        "user_id": "145246939508809147",
        "custom_user_identifier": "acme:account:1234",
        "email": "player_1@team.com",
        "type": "team",
        "status": "pending",
        "name": "A team or player name",
        "custom_fields": {
            "country": "GB",
            "twitter": "twitter_id"
        },
        "lineup": [
            {
                "name": "A team player name",
                "email": "player_1@team.com",
                "custom_user_identifier": "acme:account:1234",
                "custom_fields": {
                    "country": "GB",
                    "twitter": "twitter_id"
                }
            }
        ]
    }
]
Structure (collection)
  • id
    string

    An unique identifier for this registration

    Example: "375143143408309123"

  • tournament_id
    string

    The id of the match's tournament.

    Example: "378426939508809728"

  • participant_id
    string

    The id of the participant

    Example: "375143143408309123"

  • user_id
    string|null

    The identifier of user associate to this registration

    Example: "145246939508809147"

  • custom_user_identifier
    string|null

    An external user identifier, use the format that suits you best

    Example: "acme:account:1234"

  • email
    string

    An email (maximum 254 characters)

    Example: "player_1@team.com"

  • type
    string

    The type of participants who plays in the tournament.

    Possible values: team, player

  • status
    string

    The status of the registration

    Possible values: pending, accepted, refused, cancelled

  • name
    string

    A name (maximum 40 characters)

    Example: "A team or player name"

  • custom_fields
    object

    The values of the custom fields configured in the tournament using the machine names as keys

    For more information, please read the Custom Fields documentation.

  • lineup
    array[object]

    Optional

    A list of team players

GET /tournaments/{tournament_id}/registrations/{id}

Authorized Access

Returns a registration by the given id and tournament. If the registration does not exist or is not associated to the tournament, the endpoint will return a 404 (Not Found).

Resource URL

https://api.toornament.com/organizer/v2/tournaments/{tournament_id}/registrations/{id}

HTTP headers

  • X-Api-Key
    string

    API key of your application (see Authentication)

  • Authorization
    string

    Access token with organizer:registration scope (see Authorization)

Path parameters

  • tournament_id
    string

    The id of the tournament containing the registration

  • id
    string

    The unique identifier of the registration to retrieve

Query Parameters

This endpoint doesn't have any query parameters.

Request Body

This endpoint doesn't require a request body.

Response

[200] Registration retrieved

Example
{
    "id": "375143143408309123",
    "tournament_id": "378426939508809728",
    "participant_id": "375143143408309123",
    "user_id": "145246939508809147",
    "custom_user_identifier": "acme:account:1234",
    "email": "player_1@team.com",
    "type": "team",
    "status": "pending",
    "name": "A team or player name",
    "custom_fields": {
        "country": "GB",
        "twitter": "twitter_id"
    },
    "lineup": [
        {
            "name": "A team player name",
            "email": "player_1@team.com",
            "custom_user_identifier": "acme:account:1234",
            "custom_fields": {
                "country": "GB",
                "twitter": "twitter_id"
            }
        }
    ]
}
Structure (object)
  • id
    string

    An unique identifier for this registration

    Example: "375143143408309123"

  • tournament_id
    string

    The id of the match's tournament.

    Example: "378426939508809728"

  • participant_id
    string

    The id of the participant

    Example: "375143143408309123"

  • user_id
    string|null

    The identifier of user associate to this registration

    Example: "145246939508809147"

  • custom_user_identifier
    string|null

    An external user identifier, use the format that suits you best

    Example: "acme:account:1234"

  • email
    string

    An email (maximum 254 characters)

    Example: "player_1@team.com"

  • type
    string

    The type of participants who plays in the tournament.

    Possible values: team, player

  • status
    string

    The status of the registration

    Possible values: pending, accepted, refused, cancelled

  • name
    string

    A name (maximum 40 characters)

    Example: "A team or player name"

  • custom_fields
    object

    The values of the custom fields configured in the tournament using the machine names as keys

    For more information, please read the Custom Fields documentation.

  • lineup
    array[object]

    Optional

    A list of team players

POST /tournaments/{tournament_id}/registrations

Authorized Access

Creates a new registration. The participant type of the tournament defines whether it expects a player or a team in the request body. If the registrations are disabled or closed, the endpoint will return a 403 (Access Denied).

Resource URL

https://api.toornament.com/organizer/v2/tournaments/{tournament_id}/registrations

HTTP headers

  • X-Api-Key
    string

    API key of your application (see Authentication)

  • Authorization
    string

    Access token with organizer:registration scope (see Authorization)

Path parameters

  • tournament_id
    string

    A unique identifier of the tournament.

Query Parameters

This endpoint doesn't have any query parameters.

Request Body

New registration

Example
{
    "type": "team",
    "name": "A team or player name",
    "email": "player_1@team.com",
    "custom_user_identifier": "acme:account:1234",
    "custom_fields": {
        "country": "GB",
        "twitter": "twitter_id"
    },
    "lineup": [
        {
            "name": "A team player name",
            "email": "player_1@team.com",
            "custom_user_identifier": "acme:account:1234",
            "custom_fields": {
                "country": "GB",
                "twitter": "twitter_id"
            }
        }
    ]
}
Structure (object)
  • type
    string

    The type of participants who plays in the tournament.

    Possible values: team, player

  • name
    string

    A name (maximum 40 characters)

    Example: "A team or player name"

  • email
    string

    Optional

    An email (maximum 254 characters)

    Example: "player_1@team.com"

  • custom_user_identifier
    string|null

    Optional

    An external user identifier, use the format that suits you best

    Example: "acme:account:1234"

  • custom_fields
    object

    Optional

    The values of the custom fields configured in the tournament using the machine names as keys

    For more information, please read the Custom Fields documentation.

  • lineup
    array[object]

    Optional

    A list of team players

Response

[201] Registration created

Example
{
    "id": "375143143408309123",
    "tournament_id": "378426939508809728",
    "participant_id": "375143143408309123",
    "user_id": "145246939508809147",
    "custom_user_identifier": "acme:account:1234",
    "email": "player_1@team.com",
    "type": "team",
    "status": "pending",
    "name": "A team or player name",
    "custom_fields": {
        "country": "GB",
        "twitter": "twitter_id"
    },
    "lineup": [
        {
            "name": "A team player name",
            "email": "player_1@team.com",
            "custom_user_identifier": "acme:account:1234",
            "custom_fields": {
                "country": "GB",
                "twitter": "twitter_id"
            }
        }
    ]
}
Structure (object)
  • id
    string

    An unique identifier for this registration

    Example: "375143143408309123"

  • tournament_id
    string

    The id of the match's tournament.

    Example: "378426939508809728"

  • participant_id
    string

    The id of the participant

    Example: "375143143408309123"

  • user_id
    string|null

    The identifier of user associate to this registration

    Example: "145246939508809147"

  • custom_user_identifier
    string|null

    An external user identifier, use the format that suits you best

    Example: "acme:account:1234"

  • email
    string

    An email (maximum 254 characters)

    Example: "player_1@team.com"

  • type
    string

    The type of participants who plays in the tournament.

    Possible values: team, player

  • status
    string

    The status of the registration

    Possible values: pending, accepted, refused, cancelled

  • name
    string

    A name (maximum 40 characters)

    Example: "A team or player name"

  • custom_fields
    object

    The values of the custom fields configured in the tournament using the machine names as keys

    For more information, please read the Custom Fields documentation.

  • lineup
    array[object]

    Optional

    A list of team players

PATCH /tournaments/{tournament_id}/registrations/{id}

Authorized Access

Updates a registration by the given id. Also you can change the status into "cancelled" when is "pending" or "accepted" (and not in a stage). Whenever the registration is accepted, after update of information, registration's status will automatically change into "pending".

Resource URL

https://api.toornament.com/organizer/v2/tournaments/{tournament_id}/registrations/{id}

HTTP headers

  • X-Api-Key
    string

    API key of your application (see Authentication)

  • Authorization
    string

    Access token with organizer:registration scope (see Authorization)

Path parameters

  • tournament_id
    string

    A unique identifier of the tournament.

  • id
    string

    The unique identifier of the registration to retrieve

Query Parameters

This endpoint doesn't have any query parameters.

Request Body

Update registration

Example
{
    "name": "A team or player name",
    "email": "player_1@team.com",
    "status": "cancelled",
    "custom_user_identifier": "acme:account:1234",
    "custom_fields": {
        "country": "GB",
        "twitter": "twitter_id"
    },
    "lineup": [
        {
            "name": "A team player name",
            "email": "player_1@team.com",
            "custom_user_identifier": "acme:account:1234",
            "custom_fields": {
                "country": "GB",
                "twitter": "twitter_id"
            }
        }
    ]
}
Structure (object)
  • name
    string

    Optional

    A name (maximum 40 characters)

    Example: "A team or player name"

  • email
    string

    Optional

    An email (maximum 254 characters)

    Example: "player_1@team.com"

  • status
    string

    Optional

    The status of the registration

    Possible values: pending, accepted, refused, cancelled

  • custom_user_identifier
    string|null

    Optional

    An external user identifier, use the format that suits you best

    Example: "acme:account:1234"

  • custom_fields
    object

    Optional

    The values of the custom fields configured in the tournament using the machine names as keys

    For more information, please read the Custom Fields documentation.

  • lineup
    array[object]

    Optional

    A list of team players

Response

[200] Registration retrieved

Example
{
    "id": "375143143408309123",
    "tournament_id": "378426939508809728",
    "participant_id": "375143143408309123",
    "user_id": "145246939508809147",
    "custom_user_identifier": "acme:account:1234",
    "email": "player_1@team.com",
    "type": "team",
    "status": "pending",
    "name": "A team or player name",
    "custom_fields": {
        "country": "GB",
        "twitter": "twitter_id"
    },
    "lineup": [
        {
            "name": "A team player name",
            "email": "player_1@team.com",
            "custom_user_identifier": "acme:account:1234",
            "custom_fields": {
                "country": "GB",
                "twitter": "twitter_id"
            }
        }
    ]
}
Structure (object)
  • id
    string

    An unique identifier for this registration

    Example: "375143143408309123"

  • tournament_id
    string

    The id of the match's tournament.

    Example: "378426939508809728"

  • participant_id
    string

    The id of the participant

    Example: "375143143408309123"

  • user_id
    string|null

    The identifier of user associate to this registration

    Example: "145246939508809147"

  • custom_user_identifier
    string|null

    An external user identifier, use the format that suits you best

    Example: "acme:account:1234"

  • email
    string

    An email (maximum 254 characters)

    Example: "player_1@team.com"

  • type
    string

    The type of participants who plays in the tournament.

    Possible values: team, player

  • status
    string

    The status of the registration

    Possible values: pending, accepted, refused, cancelled

  • name
    string

    A name (maximum 40 characters)

    Example: "A team or player name"

  • custom_fields
    object

    The values of the custom fields configured in the tournament using the machine names as keys

    For more information, please read the Custom Fields documentation.

  • lineup
    array[object]

    Optional

    A list of team players

DELETE /tournaments/{tournament_id}/registrations/{id}

Authorized Access

Deletes one registration.

Resource URL

https://api.toornament.com/organizer/v2/tournaments/{tournament_id}/registrations/{id}

HTTP headers

  • X-Api-Key
    string

    API key of your application (see Authentication)

  • Authorization
    string

    Access token with organizer:registration scope (see Authorization)

Path parameters

  • tournament_id
    string

    A unique identifier of the tournament.

  • id
    string

    The id of the requested registration.

Query Parameters

This endpoint doesn't have any query parameters.

Request Body

This endpoint doesn't require a request body.

Response

[204] Success