No Data for Aegislash.

[staticaron]

Doublade's evolution and Honedge's final evolution named Aegislash doesn't have any data on the api.

Both Honedge and Doublade have their entries in the api.

Veekun's pokedex has the data and works perfectly.

Expected Behaviour:

The appropriate data should be send by the api.

Steps to Reproduce:

1.Search Aegislash on the api.

[C-Garza]

Aegislash does exist, but it has different forms so its endpoint isn't just Aegislash.

You could query by id or a specific form name like this:
https://pokeapi.co/api/v2/pokemon/681
https://pokeapi.co/api/v2/pokemon/aegislash-shield
https://pokeapi.co/api/v2/pokemon/aegislash-blade

[staticaron]

@C-Garza thanks, but one of them ( Aegislash-Shield / Aegislash-Blade ) should have a reference to one another in the forms section like the veekun pokedex :

In veekun pokedex, there is a entry for Aegislash which is Aegislash-Blade by default and references the other form.

The point is, no one knows to search Aegislash-Blade instead of Aegislash.

[Parnassius]

You can obtain the default form from the pokemon-species endpoint, in the varieties field: https://pokeapi.co/api/v2/pokemon-species/aegislash

[Kronopt]

The point is, no one knows to search Aegislash-Blade instead of Aegislash.

This is actually a pretty good point, one I've made in the past myself.
There are many issues referencing this quirk of pokeapi, and this probably won't be the last one.

Are there any issues in having a default variety for the Aegislash, instead of Aegislash-Blade, etc?

[Rrhapsod]

The same problem with Giratina. No one searches for giratina-origin

[staticaron]

The same problem with Giratina. No one searches for giratina-origin

I have made a custom json file with all the correct references. You can cache this json into a dictionary to perform quick checks.