- Game events API
Please read the overwolf.games.events documentation page to learn how to use Overwolf game events.
Sample Apps
Available Features
Game events status
It is highly recommended to communicate errors and warnings to your app users. Check game event status here, or easily check game events status from your app using our API.
gep_internal
Info Updates
key | Category | Values | Notes | Since GEP Ver. |
---|---|---|---|---|
gep_internal | gep_internal | Local + Public version number | See notes | 143.0 |
gep_internal note
Data Example:
{"info":{"gep_internal":{"version_info":"{"local_version":"157.0.1","public_version":"157.0.1","is_updated":true}"}},"feature":"gep_internal"}
collection
Info Updates
key | Category | Values | Notes | Since GEP Ver. |
---|---|---|---|---|
collection | game_info | Current card collection of the local player. | See notes | 117.1 |
collection note
- The “collection” data is available as soon as the player logs into Hearthstone.
- The collection is updated whenever the user adds/removes a card.
Example for cards "collection":
{ CS2_065: "{"id" : "CS2_065", "count" : "1", "premiumCount" : "0" }",
CS1_113: "{"id" : "CS1_113", "count" : "2", "premiumCount" : "0" }",
NEW1_011: "{"id" : "NEW1_011", "count" : "2", "premiumCount" : "0" }",
EX1_131: "{"id" : "EX1_131", "count" : "1", "premiumCount" : "2" }",
CS2_121: "{"id" : "CS2_121", "count" : "2", "premiumCount" : "0" }",
…
}
"Card" structure:
{ "id" : "card_id" , "count" : "int" , "premiumCount" : "int" }
- “id” – The card’s id
- “count” – The number of regular cards
- “premiumCount” – The number of premium (golden) cards
scene_state
Info Updates
key | Category | Values | Notes | Since GEP Ver. |
---|---|---|---|---|
scene_state | game_info | Current game scene. | See notes | 117.1 |
scene_state note
Can be one of the following:
- scene_startup
- scene_login
- scene_hub
- scene_gameplay
- scene_collectionmanager
- scene_packs
- scene_tournament
- scene_friendly
- scene_fatal_error
- scene_draft
- scene_credits
- scene_reset
- scene_adventure
- scene_tavern_brawl
decks
Info Updates
key | Category | Values | Notes | Since GEP Ver. |
---|---|---|---|---|
[deck_id] | decks | The “decks” feature provides data about the currently “visible” decks. | See notes | 119.1 |
selected_deck | selected_deck | The selected deck. | See notes | 119.1 |
Adventure Deck | decks | The currently played deck on adventure mode. | See notes | 143.0 |
adventure_loot_options | decks | The currently offered 3-option draft (between bosses) | See notes | 143.0 |
deck_id note
The key is the deck's deck_id
string. It is not the literal string "deck_id". See the example below.
Decks are “visible” when the local player starts a new game, during the “deck selection” screen, or when the local player enters the “My Collection” menu. The following data is being provided for each deck:
- Deck name/id
- Deck cards (array of cards)
- Deck key
“Card” structure:
{ "id" : "card_id", "count" : "int", "premiumCount" : "int" }
- “id” – The card's id
- “count” – The number of regular cards
- “premiumCount” – The number of premium (golden) cards
Example for a “deck_id” info-update structure:
{
"info":{
"decks":{
"Mage":"{
\"deck_id\":\"Mage\",
\"cards\":[
{\"id\":\"BOT_573\",\"count\":1,\"premiumCount\":0},
{\"id\":\"CS2_024\",\"count\":2,\"premiumCount\":0},
{\"id\":\"CS2_033\",\"count\":1,\"premiumCount\":0},
...
{\"id\":\"UNG_845\",\"count\":1,\"premiumCount\":0},
{\"id\":\"UNG_941\",\"count\":1,\"premiumCount\":0}
],
\"deck_key\":\"adventure_deck\"
}"
}
},
"feature":"decks"
}
Arena Decks, unlike standard decks, will be updated each time the local player chooses a card during the Arena Draft phase.
selected_deck note
The following data is provided when the local player selects a deck:
- “deck_id”
- “deck_name”