Alchemy API

Enterprise Grade API for Ethereum

Jumpstart your Ethereum development with Alchemy!
Instead of running your own nodes and building your own architecture,
just plug into our API and get back to focusing on developing
your application.

Get Started

Cheeze Wizards API

Alchemy's API allows Cheeze Wizard developers to interact with simple, intuitive endpoints and access information about wizards, duels and more.

Learn More →

Getting Started

To start making requests to the Alchemy Cheeze Wizards API, all you'll need is a valid API key and a verified email address. To get your key, just sign up on the Cheeze Wizards developer page and you'll receive one via email. After that, you can use the API endpoints below to get all of the currently released on-chain Cheeze Wizards data.

If at any point you have question, comments, or need support, join us on Telegram. We're happy to help!

NOTE - All requests must have the following headers:

-H "Content-Type: application/json" \
-H "x-api-token: your-api-token" \
-H "x-email: your-email@email.com"

GET Wizard by Id

# Request
curl -X GET "https://cheezewizards.alchemyapi.io/wizards/1" \
-H "Content-Type: application/json" \
-H "x-api-token: your-api-token" \
-H "x-email: your-email@email.com"
// Result
{
  "id":"1",
  "owner":"0xF0128825b0c518858971d8521498769148137936",
  "affinity":1,
  "startingPower":"777000000000000",
  "power":"777000000000000",
  "eliminatedBlockNumber":null,
  "createdBlockNumber":7914701,
}

Path Variable

id - the wizard's Id

Returns

id - the wizard's Id
owner - the address of the wizard's owner
affinity - the wizard's affinity: 0 = NOTSET, 1 = NEUTRAL, 2 = FIRE, 3 = WIND, 4 = WATER
startingPower - the wizard's initial power at the time of creation
power - the wizard's current power
eliminatedBlockNumber - the block number where the wizard was eliminated, null if the wizard is still alive
createdBlockNumber - the block number where the wizard was created

More return values coming soon! Once the Cheeze Wizard tournament contracts are live, we will also return:
currentDuel - duel that the wizard is currently involved in if any
isAscending - true if the wizard is ascending, false otherwise
ascensionOpponent - duel opponent if ascending
molded - true if molded (dead), false if otherwise (alive)

GET Wizards by affinity, power, owner

# Request
curl "https://cheezewizards.alchemyapi.io/wizards?affinity=4&owner=0xF0128825b0c518858971d8521498769148137936&minPower=100000&maxPower=900000000000000" \
-H "Content-Type: application/json" \
-H "x-api-token: your-api-token" \
-H "x-email: your-email@email.com"
// Result 
{
  "wizards":[{"id":"3","owner":"0xF0128825b0c518858971d8521498769148137936","affinity":4,"power":"420000000000000"},{"id":"33","owner":"0xF0128825b0c518858971d8521498769148137936","affinity":4,"power":"420000000000000"}, ...]
}

Query Parameters

All query parameters are optional.

owner - wizards owned by this address
affinity - wizards with this affinity: 0 = NOTSET, 1 = NEUTRAL, 2 = FIRE, 3 = WIND, 4 = WATER
minPower - wizards whose power is greater than or equal to minPower
maxPower - wizards whose power is less than or equal to maxPower

More query parameters coming soon:
isAlive - true for wizards that are alive, false otherwise
isAscending - true for wizards that are ascending, false otherwise

Returns

wizards - a list of wizards


NOTE - This duel endpoint is coming soon! Once the Cheeze Wizard tournament contracts are live, this endpoints will be live.

GET Duel by Id

# Request
curl -X GET "https://cheezewizards.alchemyapi.io/duels/1" \
-H "Content-Type: application/json" \
-H "x-api-token: your-api-token" \
-H "x-email: your-email@email.com"
// Result
{
  "duelId":"1",
  "wiz1Id":"3",
  "wiz2Id":"4",
  "startBlock":"8262503",
  "endBlock":"8262507",
  "isAscensionBattle":"true",
  "moveSet1": "1,3,2",
  "moveSet2": "1,2,3",
  "power1":"320000000000000",
  "power2":"620000000000000",
  "timedOut":"false",
}

Path Variable

id - the duel Id

Returns

duelId - the duel Id
wiz1Id - the first wizard involved in the battle
wiz2Id - the second wizard involved in the battle
startBlock - the block number the duel started on
endBlock - the block number the duel ended on, null if the duel is in progress
isAscensionBattle - true if the duel is with an ascending wizard, false otherwise
moveSet1 - moves used by the first wizard during the duel
moveSet2 - moves used by the second wizard during the duel
power1 - the power of the first wizard after the duel, null if the duel is in progress
power2 - the power of the second wizard after the duel, null if the duel is in progress
timeoutBlock - the block number at which the duel will time out
timedOut - true if the duel timed out, false otherwise


NOTE - This duel endpoint is coming soon! Once the Cheeze Wizard tournament contracts are live, this endpoints will be live.

GET Duels by block, wizard, status

# Request
curl "https://cheezewizards.alchemyapi.io/duels?startsAfter=8262502&wizardIds=3,4" \
-H "Content-Type: application/json" \
-H "x-api-token: your-api-token" \
-H "x-email: your-email@email.com"
// Result 
{
  "duels":[{"duelId":"1","wiz1Id":"3","wiz2Id":"4","startBlock":8262503,"endBlock":8262507,"isAscensionBattle":"true","moveSet1": "1,3,2","moveSet2": "1,2,3","power1":320000000000000,"power2":620000000000000, "timedOut":true}, ...]
}

Query Parameters

All query parameters are optional.

startsAfter - duels that start after this block number
startsBefore - duels that start before this block number
endsAfter - duels that end after this block number
endsBefore - duels that end before this block number
wizardIds - duels involving these wizards (coma separated list of wizardIds)
excludeInProgress - true for completed duels, false for all duels (default)
excludeFinished - true for duels in progress, false for all duels (default)

Returns

duels - a list of duels

Cheeze Wizards API


Alchemy's API allows Cheeze Wizard developers to interact with simple, intuitive endpoints and access information about wizards, duels and more.

Learn More →

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.