Participant API › Participants Legacy
LegacyGET /me/participants
This endpoint is in legacy mode. Access will soon be deprecated. It is therefore advised to use another endpoint when possible.
Returns the participants linked to the user associated to the access token.
Resource URL
https://api.toornament.com/participant/v2/me/participants
HTTP headers
- X-Api-Keystring
API key of your application (see Authentication)
- Authorizationstring
Access token with
participant:manage_participations
scope (see Authorization) - Rangestring
A range of requested items using the
participants
unit. The size of the range can not exceed 50. (see Pagination)Example: participants=0-49
Query Parameters
- tournament_idsarray
Only return participants for the given list of tournaments.
Example: 378426939508809728,534138941862841533
- playlist_idsarray
Only return participants for the tournaments listed in the playlist.
Example: 123485236848698874,135864989139387313
Request Body
This endpoint does not require a request body.
Response
[206] Participants retrieved.
Example
[ { "lineup": [ { "name": "Jon Snow", "email": "[email protected]", "custom_fields": {} } ], "id": "375143143408309123", "tournament_id": "378426939508809728", "type": "team", "name": "Northmen", "custom_fields": {}, "checked_in": true, "checked_in_at": "2015-12-32T13:37:42+00:00" } ]
Structure (collection)
- lineuparray[object]
A list of players in a team (Only if the tournament participant type is “team”).
- idstring
The id of the participant.
Example: "375143143408309123"
- tournament_idstring
The id of the tournament that contains this participant.
Example: "378426939508809728"
- typestring
The type of participants that play in the tournament.
Possible values: team, player
- namestring
The name of the participant.
Max. length: 40 characters
Example: "Northmen"
- custom_fieldsobject
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.
Example: {}
- checked_inboolean
Whether the participant is checked in.
Example: true
- checked_in_atstring|null
The date and time of the participant check-in, in RFC 3339 format (combined date, time and utc offset).
Format: datetime
Example: "2015-12-32T13:37:42+00:00"
LegacyGET /me/participants/{id}
This endpoint is in legacy mode. Access will soon be deprecated. It is therefore advised to use another endpoint when possible.
Returns the participant with the given id on the condition that it is associated to the authenticated user, else the endpoint will return a 403 Error (Forbidden).
Resource URL
https://api.toornament.com/participant/v2/me/participants/{id}
HTTP headers
- X-Api-Keystring
API key of your application (see Authentication)
- Authorizationstring
Access token with
participant:manage_participations
scope (see Authorization)
Path parameters
- idstring
The id of the participant to retrieve.
Query Parameters
This endpoint does not have any query parameters.
Request Body
This endpoint does not require a request body.
Response
[200] Participant retrieved.
Example
{ "lineup": [ { "name": "Jon Snow", "email": "[email protected]", "custom_fields": {} } ], "id": "375143143408309123", "tournament_id": "378426939508809728", "type": "team", "name": "Northmen", "custom_fields": {}, "checked_in": true, "checked_in_at": "2015-12-32T13:37:42+00:00" }
Structure (object)
- lineuparray[object]
A list of players in a team (Only if the tournament participant type is “team”).
- idstring
The id of the participant.
Example: "375143143408309123"
- tournament_idstring
The id of the tournament that contains this participant.
Example: "378426939508809728"
- typestring
The type of participants that play in the tournament.
Possible values: team, player
- namestring
The name of the participant.
Max. length: 40 characters
Example: "Northmen"
- custom_fieldsobject
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.
Example: {}
- checked_inboolean
Whether the participant is checked in.
Example: true
- checked_in_atstring|null
The date and time of the participant check-in, in RFC 3339 format (combined date, time and utc offset).
Format: datetime
Example: "2015-12-32T13:37:42+00:00"
LegacyPATCH /me/participants/{id}
This endpoint is in legacy mode. Access will soon be deprecated. It is therefore advised to use another endpoint when possible.
Updates the participant with the given id on the condition that it is associated to the authenticated user, else the endpoint will return a 403 Error (Forbidden).
Resource URL
https://api.toornament.com/participant/v2/me/participants/{id}
HTTP headers
- X-Api-Keystring
API key of your application (see Authentication)
- Authorizationstring
Access token with
participant:manage_participations
scope (see Authorization)
Path parameters
- idstring
The id of the participant to retrieve.
Query Parameters
This endpoint does not have any query parameters.
Request Body
Participant data.
Example
{ "checked_in": true }
Structure (object)
- checked_inboolean
Optional
If you confirm the check-in, you will not be able to go back.
Example: true
Response
[200] Participant update.
Example
{ "lineup": [ { "name": "Jon Snow", "email": "[email protected]", "custom_fields": {} } ], "id": "375143143408309123", "tournament_id": "378426939508809728", "type": "team", "name": "Northmen", "custom_fields": {}, "checked_in": true, "checked_in_at": "2015-12-32T13:37:42+00:00" }
Structure (object)
- lineuparray[object]
A list of players in a team (Only if the tournament participant type is “team”).
- idstring
The id of the participant.
Example: "375143143408309123"
- tournament_idstring
The id of the tournament that contains this participant.
Example: "378426939508809728"
- typestring
The type of participants that play in the tournament.
Possible values: team, player
- namestring
The name of the participant.
Max. length: 40 characters
Example: "Northmen"
- custom_fieldsobject
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.
Example: {}
- checked_inboolean
Whether the participant is checked in.
Example: true
- checked_in_atstring|null
The date and time of the participant check-in, in RFC 3339 format (combined date, time and utc offset).
Format: datetime
Example: "2015-12-32T13:37:42+00:00"