What do you mean?
Yes I know, that but the point is that the resource POST /api/auctions/:page/:number with the body could be simply converted as query parameters this way:
/api/auctions/:page/:number ==> /api/auctions?page=1&resultsPerPage=1
Reason: the resource you are waintg to retrieve is "auctions", not the "number"
Also change "number" to "resultsPerPage", which is more clear as user. Can set a defalut number of "30" or just make it mandatory.
You can make "page" it mandatory giving a 4XX error and feedback.
input ==> cardName. Query param also
Reason: More semantical name, excep for technical limitations no extra info is required, the names gives all the meta info needed
Optional
min ==> minBfpPrice. Query param also
Reason: More semantical name, excep for technical limitations no extra info is required, the names gives all the meta info needed
Optional
max ==> maxBfpPrice. Query param also
Reason: More semantical name, excep for technical limitations no extra info is required, the names gives all the meta info needed
Optional
Having this all together the
"POST /api/auctions/:page/:number" + "Body" can be a simple
"GET /api/auctions?page=1&resultsPerPage=1&cardName=Master Archers&minBfpPrice=12&maxBfpPrice=30000" and no Body is required
This being told, I don't want to make enemies but to give feedback as person that wants to use this and finds it usable, but not mostly correct. I find this approach clearer and easily expandable wityh more filters in the future if it's required.
If it's a problem of change it, give me access to a feature branch and I gladly will make the changes and send de merge request (logically the final decison will be yours to apply it)
I'll post the same on the issues page from github, I just wanted to give a more direct developer-friendly response.
Thank you for your hard work,
fellow Skylord.