Documentation - PokéAPI

Information

A free rate-limited endpoint is available at graphql.pokeapi.co/v1beta2. This endpoint can be subject to changes in the future. Only POST requests are allowed.

To ease learning and developing, a GraphiQL interface is hosted at graphql.pokeapi.co/v1beta2/console/. This console loads PokeAPI's GraphQL schema and offers a handy Explorer that can be used to create GraphQL queries. GraphQL queries are still HTTP queries so you can use your favorite tool/library to query the GraphQL endpoint. Follows an example using Curl.


# This curl retrieves all items and relative costs
curl 'https://graphql.pokeapi.co/v1beta2' \
-H 'content-type: application/json' \
-H 'accept: */*' \
--compressed \
--data-binary @- << EOF
{
    "query": "query getItems{item{name,cost}}",
    "variables": null,
    "operationName":"getItems"
}
EOF

A Node example and some GQL queries are available here.

v1beta2

A new specification v1beta2 has been released on June 2025. The major change is that the prefix pokemon_v2_ has been stripped away from all types so to have a clearer way to build GQL queries. A GraphiQL console can be found at graphql.pokeapi.co/v1beta2/console

v1beta

This v1beta specification is sun-setting and scheduled to be removed in summer 2025. A GraphiQL console can still be found at beta.pokeapi.co/graphql/console

Fair Use

PokéAPI is free and open to use. It is also very popular. Because of this, we ask every developer to abide by our fair use policy. People not complying with the fair use policy will have their IP address permanently banned.

PokéAPI is primarily an educational tool, and we will not tolerate denial of service attacks preventing people from learning.

Rules:

Locally cache resources whenever you request them.
Be nice and friendly to your fellow PokéAPI developers.
If you spot security vulnerabilities act and report them responsibly.

Beta status

To reduce costs we are hosting the GraphQL API on a GCP e2-micro free instance. The machine can hardly support all the load of Hasura and Postgres thanks to some ingenious tweaks.

Nonetheless, this has a cost to the user experience. A 100 calls/h per IP rate-limit is put in place, the instance is set to reboot every day at 1 AM UTC with a consequent 2 minutes of downtime, every successful HTTP response is cached server-side, sporadic maintenance and testing might stop the service.