Webhooks
Webhooks are POST messages from FACEIT to your own server. You must configure a valid REST endopoint to receive Webhooks.
Subscribing to Webhooks
You can create subscriptions in the "Webhooks" section of the App Studio. There are multiple Webhooks organized by Subscription Type, based on the specific events exposed and restrictions enforced.
Subscription Types
Organizer
These scopes are available for the selected subscription type:
- All my organizers: The subscription will span across all your organizers and will be kept automatically up-to-date based on your account changes
- Static list of my organizers: The subscription will span across a static list of your organizers. You must select one or more organizers in the select field below
- Static list of other organizers: The subscription will span across a static list of other organizers. You can add any organizer GUID available on the FACEIT platform. Some event details (such as private information) may be hidden
User
These scopes are available for the selected subscription type:
My user: The subscription will only include your user Static list of other users: The subscription will span across a static list of other users. You can add any user GUID available on the FACEIT platform. Some event details (such as private information) may be hidden
Game
These scopes are available for the selected subscription type:
Static list of my games: The subscription will span across a static list of your games. You must select one or more games in the select field below
Events
Event | Organizer | User | Game |
---|---|---|---|
hub_created | Χ | Χ | |
hub_role_created | Χ | Χ | |
hub_role_deleted | Χ | Χ | |
hub_role_updated | Χ | Χ | |
hub_updated | Χ | Χ | |
hub_user_added | Χ | Χ | |
hub_user_invited | Χ | Χ | |
hub_user_removed | Χ | Χ | |
hub_user_role_added | Χ | Χ | |
hub_user_role_removed | Χ | Χ | |
match_object_created | Χ | Χ | Χ |
match_status_aborted | Χ | Χ | Χ |
match_status_cancelled | Χ | Χ | Χ |
match_status_configuring | Χ | Χ | Χ |
match_status_finished | Χ | Χ | Χ |
match_status_ready | Χ | Χ | Χ |
match_demo_ready | Χ | Χ | Χ |
tournament_object_created | Χ | Χ | |
tournament_object_removed | Χ | Χ | |
tournament_object_updated | Χ | Χ | |
tournament_status_cancelled | Χ | Χ | |
tournament_status_checkin | Χ | Χ | |
tournament_status_finished | Χ | Χ | |
tournament_status_seeding | Χ | Χ | |
tournament_status_started | Χ | Χ |
Callback
In this section you can specify the REST endpoint that is going to receive the Webhooks.
Authentication is optional, but recommended. You can specifiy either:
- Header Name + Header Value, or
- Query string parameter + Query string value, or
- Both
The implementation of a specific security logic is something that you as a developer must implement in your code.