PokeAPI is a free, public RESTful API that serves comprehensive data about the Pokémon universe, including Pokémon abilities, berries, characteristics, contest types and effects, egg groups, and encounter methods and conditions. All resources are fully open and returned as JSON, making it a convenient source for reference and reporting data.
Power end-to-end data operations for your PokeAPI API with Nexla. Our bi-directional PokeAPI connector is purpose-built for PokeAPI, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to PokeAPI or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your PokeAPI workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
PokeAPI is a free, public API, and no authentication or API key is required to access its resources. All endpoints are served over HTTPS from the base URL https://pokeapi.co/api/v2/ and return read-only JSON data.
To connect Nexla to PokeAPI:
No account creation or credential sign-up is needed with PokeAPI itself. You can begin building a data source immediately.
The Nexla PokeAPI connector supports optional API Key or Basic Authentication credentials. Supply these only if your organization fronts PokeAPI with a proxy or gateway that enforces its own authentication; for the public PokeAPI service, these fields are not required.
Review the PokeAPI fair-use policy. PokeAPI asks consumers to locally cache resources and to keep request frequency reasonable, since the service is community-funded. Nexla schedules and paginates requests, which helps you stay within these guidelines.
For the full list of resources, response structures, and pagination parameters, see the PokeAPI v2 Documentation.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Select the authentication method you want to use, and enter the required values. For the public PokeAPI service, authentication values are not required; provide them only if your deployment proxies PokeAPI through a gateway that enforces authentication.
PokeAPI is a free, public API and does not require authentication for its hosted endpoints. The API Key and Basic Authentication methods are provided for deployments that place an authentication layer in front of PokeAPI.
For details on available resources, response structures, and pagination, see the PokeAPI v2 Documentation.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the PokeAPI connector tile, then select the credential that will be used to connect to PokeAPI, and click Next; or, create a new PokeAPI credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common PokeAPI endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List abilities
This endpoint template retrieves a paginated list of Pokémon abilities. Use this template when you need to enumerate the available abilities, such as to build a reference list or to collect ability identifiers for subsequent lookups.
The list endpoint returns summary entries with a name and URL for each ability, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get an ability
This endpoint template retrieves the full details for a single Pokémon ability by its name or ID. Use this template when you need the complete record for a specific ability, including its effect text and the Pokémon that can have it.
[Rest API] List berries
This endpoint template retrieves a paginated list of berries. Use this template to enumerate the available berries and collect their identifiers for subsequent detail lookups.
The list endpoint returns summary entries with a name and URL for each berry, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get a berry
This endpoint template retrieves the full details for a single berry by its name or ID, including its growth time, size, firmness, flavors, and natural gift power.
[Rest API] List berry firmness
This endpoint template retrieves a paginated list of berry firmness levels. Use this template to enumerate the available firmness categories used to classify berries.
The list endpoint returns summary entries with a name and URL for each firmness level, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get a berry firmness
This endpoint template retrieves the full details for a single berry firmness level by its name or ID, including the list of berries that share that firmness.
[Rest API] List berry flavors
This endpoint template retrieves a paginated list of berry flavors. Use this template to enumerate the available flavors that berries can have and that influence Pokémon nature preferences.
The list endpoint returns summary entries with a name and URL for each flavor, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get a berry flavor
This endpoint template retrieves the full details for a single berry flavor by its name or ID, including the berries associated with that flavor and their potency.
[Rest API] List characteristics
This endpoint template retrieves a paginated list of Pokémon characteristics. Characteristics indicate a Pokémon's highest individual stat value.
The list endpoint returns summary entries with a URL for each characteristic, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get a characteristic
This endpoint template retrieves the full details for a single characteristic by its ID, including the associated stat and the possible gene modulo values.
[Rest API] List contest types
This endpoint template retrieves a paginated list of contest types. Contest types are categories judges use to evaluate a Pokémon's moves in contests.
The list endpoint returns summary entries with a name and URL for each contest type, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get a contest type
This endpoint template retrieves the full details for a single contest type by its name or ID, including its associated berry flavor and localized names.
[Rest API] List contest effects
This endpoint template retrieves a paginated list of contest effects. Contest effects define the appeal and jam values a move produces in a contest.
The list endpoint returns summary entries with a URL for each contest effect, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get a contest effect
This endpoint template retrieves the full details for a single contest effect by its ID, including its appeal, jam, and effect descriptions.
[Rest API] List egg groups
This endpoint template retrieves a paginated list of egg groups. Egg groups are categories that determine which Pokémon are able to interbreed.
The list endpoint returns summary entries with a name and URL for each egg group, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get an egg group
This endpoint template retrieves the full details for a single egg group by its name or ID, including the Pokémon species that belong to it.
[Rest API] List encounter methods
This endpoint template retrieves a paginated list of encounter methods. Encounter methods describe the ways a player can come across a wild Pokémon.
The list endpoint returns summary entries with a name and URL for each encounter method, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get an encounter method
This endpoint template retrieves the full details for a single encounter method by its name or ID, including its display order and localized names.
[Rest API] List encounter conditions
This endpoint template retrieves a paginated list of encounter conditions. Encounter conditions are situations that affect which wild Pokémon can appear, such as time of day.
The list endpoint returns summary entries with a name and URL for each encounter condition, and supports limit/offset pagination. Nexla will follow pagination to fetch subsequent pages of data.
[Rest API] Get an encounter condition
This endpoint template retrieves the full details for a single encounter condition by its name or ID, including its possible condition values and localized names.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
PokeAPI data sources can also be manually configured to ingest data from any valid PokeAPI endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new PokeAPI data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
