All integrationsGaming

HearthstoneJSON

Read Hearthstone's card data from a workflow.

actions
12

Actions

Steps a workflow can run in HearthstoneJSON.

  • Search cardsSearch every Hearthstone card by text and by every property a card has: set, class, type, rarity, minion type, spell school, keyword, mana cost, attack and health. Each card comes back with its rules text in plain form, its keywords spelled out, and its art, tile and render URLs already built, so a step can post a card without a second call. This is the action to reach for first: it turns 'legendary Dragon minions that cost seven or less' into the cards themselves. Reads the collectible set unless told otherwise. No API key required.
  • Get a cardGet one Hearthstone card in full, by its name, its card ID or its dbfId: 'Leeroy Jenkins', 'EX1_116' and 559 all find the same card. Every field the game publishes comes back, from the rules text and the flavour joke to the play requirements and the pool a card creates from, along with every image URL. A card the collectible set does not hold, such as a hero power or an enchantment, is looked for in the whole game rather than reported missing. No API key required.
  • Get a random cardPick a card at random out of everything the filters leave, or a handful of them. The filters are the ones Search cards takes, so a step can ask for a random Legendary from one expansion, or a random Murloc, rather than a random anything. Built for the workflows that post a card of the day or open a meeting with one. An empty pool is reported as found: false with the filters that produced it, rather than as a failed step. No API key required.
  • List card setsList every set in the game with how many cards it holds, how many of those are collectible, and which classes it touches. This is the step that turns 'the Un'Goro expansion' into the set code the other actions filter on, and the quickest way to see what a new patch added. No API key required.
  • List keywordsList every keyword the cards use, with how many carry each one and an example. Battlecry, Deathrattle, Taunt, Discover and the rest, including the ones a new expansion introduced. This is where the values the keyword filter takes come from, and it answers 'how many Taunt minions are there' on its own. No API key required.
  • Get related cardsGet the cards one card brings with it: the pool it creates from, the hero power a hero comes with, and the tokens and enchantments it summons or applies. Nothing in the card data links those last ones, so they are found through the game's own ID convention, which is what turns 'Leeroy Jenkins' into the 1/1 Whelps he gives your opponent. Reads the whole game, since none of these are collectible. No API key required.
  • Summarize cardsBreak a slice of the card pool down by every property at once: how it splits across classes, sets, types, rarities, minion types, spell schools and keywords, its mana curve, and its average cost, attack and health. Takes the same filters as Search cards, so a step can ask what one expansion gave each class, or how aggressive a class's cards are, without pulling the cards themselves. No API key required.
  • Get card imagesGet every image HearthstoneJSON publishes for one card: the square art at both sizes in JPG and WebP, the lossless original, the deck-list tile in three formats, and the whole card rendered in any of the game's languages. Each URL comes back with what it is and whether the service publishes it for this card, since only playable cards are pre-rendered. Use it when a step needs a link to embed; use Download a card image when it needs the file. No API key required.
  • Download a card imageDownload one of a card's images and store it, so a later step can attach it to an email, post it or put it in a document. Choose the whole rendered card, the square art at either size, the lossless original or the deck-list tile. Asking for a render of a card the service does not pre-render comes back as a sentence naming what to ask for instead, rather than as a 404. HearthstoneJSON asks that busy sites re-host rather than hotlink, which is what this action is for. No API key required.
  • Get enum valuesRead the enumerations behind the card data. Every set code, class, card type, rarity, minion type and game tag is one member of one of these, so this is where a value the filters did not offer comes from, and how a number in another Hearthstone tool is turned back into a name. Leave the enumeration empty to see which ones the service publishes. No API key required.
  • List languagesList every language HearthstoneJSON publishes card text in, each with the file it lives in. Read from the service's own list rather than a fixed one, so a language added later shows up here. Run it once when building a workflow that has to report cards in something other than English. No API key required.
  • Get the latest buildFind out which game build HearthstoneJSON is publishing right now, how many collectible cards and sets it holds, and which sets are newest. The build number is what pins the rest of a workflow to one patch, so every step reads the same cards even if a patch lands mid-run, and comparing it against a build recorded earlier is how a workflow notices that a new expansion is out. No API key required.

Automate HearthstoneJSON with Lodol.

Connect HearthstoneJSON and ask your AI for your first workflow.

Free plan, no credit card