/move/371/ returns a 404, but /move/371 works

PokeAPI / pokeapi

The Pokémon API

https://pokeapi.co

BSD 3-Clause "New" or "Revised" License

4.31k stars 952 forks source link

/move/371/ returns a 404, but /move/371 works #574

Closed richard-yin closed 3 years ago

richard-yin commented 3 years ago

Steps to Reproduce:

Try to query /move/371/ with any browser or application.

/move/371, /move/370/, and /move/372/ all seem to work properly. This broke the wrapper I was using since /pokemon/amoonguss has the affected URL in its move list.

evayde commented 3 years ago

Same with

location-area/168/ and location-area/168

blfunex commented 3 years ago

Same with https://pokeapi.co/api/v2/pokemon/4/ and https://pokeapi.co/api/v2/pokemon/4.

efoerster commented 3 years ago

Found the opposite behavior: /item/antidote returns 404 but /item/antidote/ works.

Naramsim commented 3 years ago

Hello,

this issue was resolved by https://github.com/PokeAPI/deploy/pull/23