Timeline for API endpoint POST vs GET
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2020 at 8:57 | answer | added | bernie | timeline score: 2 | |
| Feb 18, 2020 at 13:17 | comment | added | Lie Ryan | SortBy is easy: SortBy=-serial,+id | |
| Feb 17, 2020 at 18:16 | comment | added | Ewan | select000000000000000000000001=eh&select000000000000000000000002=... | |
| Feb 17, 2020 at 18:12 | answer | added | Ewan | timeline score: 2 | |
| Feb 17, 2020 at 18:00 | history | tweeted | twitter.com/StackSoftEng/status/1229465714974691333 | ||
| Feb 17, 2020 at 17:13 | vote | accept | Casey Crookston | ||
| Feb 17, 2020 at 16:57 | answer | added | Esben Skov Pedersen | timeline score: 9 | |
| Feb 17, 2020 at 16:50 | comment | added | Jory Geerts | As per stackoverflow.com/questions/417142/… you have 2000 characters for the whole URL. Subtract about 100 for the domainname, path, etc. and there is still plenty of space left for your entire question. | |
| Feb 17, 2020 at 16:49 | comment | added | Casey Crookston | @JonRaynor, thanks. After googling the correct thing, I finally found this: stackoverflow.com/questions/14202257/… which pretty much says what you said. It's okay to use POST in a case like this. | |
| Feb 17, 2020 at 16:47 | comment | added | Jon Raynor | If your search parameters can't be accommodated via a query string, go with a post. I can't predict what the future needs of your application will be. Certainly a POST will be able to handle more information than a query string. | |
| Feb 17, 2020 at 16:41 | comment | added | Casey Crookston | @JonRaynor, thanks but I'm not sure how that applies to my question here. That questions is: Can I pass a body with a GET call. That's not what I am asking here. | |
| Feb 17, 2020 at 16:37 | comment | added | Jon Raynor | stackoverflow.com/questions/978061/http-get-with-request-body | |
| Feb 17, 2020 at 16:28 | history | asked | Casey Crookston | CC BY-SA 4.0 |