Why Some Companies Require All APIs to Use POST Requests
The article examines why certain companies mandate POST for every API endpoint, comparing GET and POST differences such as security, payload size, data types, speed, intended usage, and caching, and concludes that POST suits large data submissions while GET is better for simple queries and static resources.
While browsing Zhihu, the author encountered the question “Why does the company require all interfaces to use POST requests?” and reflected on personal experience building a microservice and applying RESTful conventions.
The author reviews the differences between GET and POST requests:
POST is more secure because parameters are not part of the URL, avoiding caching, server logs, and browser history.
POST can carry larger payloads; GET is limited by URL length.
POST supports more data types, while GET is limited to ASCII characters.
POST is slower than GET.
POST is intended for creating or modifying data; GET is typically used for searching, sorting, or filtering.
GET requests for static resources may be cached, whereas data requests are not.
From these points, POST is advantageous for large data submissions, while GET is better for retrieving static resources or simple queries.
The author personally uses GET for simple queries and POST for create, update, delete, or complex queries, but does not enforce POST for every endpoint.
Some community members suggest following industry best practices, while others criticize the policy as catering to low‑skill architects and developers.
Finally, the article asks readers what API policy they would adopt in their own company.
Architecture Digest
Focusing on Java backend development, covering application architecture from top-tier internet companies (high availability, high performance, high stability), big data, machine learning, Java architecture, and other popular fields.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.