Features like filtering or searching don’t automatically come with every endpoint, if the API hasn’t been implemented that way then it would never work.
As that’s a public test example endpoint, the functionality for it is quite limited. You can find the basic docs here:
I see thank you for this, so there isn’t another way of doing it can you not specify something in the body with a java script very curious about that. Asking this what happens if a client gives you an api like the test one I used was wondering how would I handle that if that is one of my tests.
Each APIs implementation is different - There could be filtering using the URL Params or possibly as part of the Request Body. The person/team who created it will know what it should and shouldn’t do.
Just taking those 2 example APIs, they are quite simple in terms of complexity but both have been implemented differently and the functionality for each one is not the same.
Ideally, you would have documentation for the whole API that would specify the behaviour of each endpoint. Without that, it’s just guesswork.