Ask HN: Current best practices when POST as GET seems unavoidable?

2 points

9 years ago

When the concern of "very long URLs" rears its head (and just won't go away) in REST API design discussions for read-only endpoints, and when there's enough time for careful planning of a new or overhauled API, what are the best practices in 2017 for using POST as if it were GET?

The following answer on Stack Overflow seems to have merit, but what strategies are really working well for you real world API implementers?

https://stackoverflow.com/questions/30767665/how-to-be-restful-with-long-urls/30773811#30773811

It would be nice if "use GraphQL instead" was an option, but let's assume it must be a plain old REST-ish HTTP API.

6 comments