Appointment Trader
Sign In
Developers
Partners
Make ~/location/set_listing operate against HTTP POST
|
By 🥩 @FamousStation67, 06/25/2023 6:09 pm
|
|
I see the "set_listing" end-point is currently operating against an HTTP GET. This should be a POST end-point in my opinion, as we'll likely hit query string limits on the query string via a GET. Would you be open to making it a POST end-point?
22 views
0 thumbs up
|
1 Answer
0 Comments |
Give the best answer |
The best answer has not been selected yet.
but at least 3 Thumbs Up's from other users is selected as the best answer.
10 Posts of the entire Community with the most, but at least 5 Thumbs Up's will appear in the
Best Posts section of .Being in the Best Posts section comes with perks, the asking user and the person who answered will both receive Traderpoints for every paid AppointmentTrader transaction at .
Traderpoints can be used to pay for Transactions on AppointmentTrader.
Check out the AppointmentTrader Communities to learn how users convert Traderpoints to cash.
|
Answer from 🥷🏻 @ColorfulRod45 (06/30/2023 8:41 am)
|
|
Hey @FamousStation67, thank you for testing the first endpoint - and sorry for being so slow to respond, I don't know why I missed the thread.
For ease of access for new developers all requests are designed to be accessible with a simple get request (which does help some people who are more scripters than coders), with that in mind request have been designed to not exceed the GET parameter limit (files, for instance are passed in as a URL which is then retrieved from the API rather than expecting a multipart-form-data request which includes the file.)
That being said - your request is absoluty valid and who knows, there might be an edgecase which would exhaust GET limits - therefore the API can now be accessed with either a regular GET request or POST on all endpoints.
If a request is POST x-www-form-urlencoded keys are prioritized over provided GET keys.
Thank you for contributing!
0 Thumbs Up
|
0 Comments
|
Comment |