Files
api-guidelines/protocol/separate-concerns.md
apidesigner 4526f3d8a3 Updates protocol/separate-concerns.md
Auto commit by GitBook Editor
2017-02-14 14:46:41 +00:00

2.4 KiB
Raw Blame History

Separate Concerns

Every API using HTTP/S API MUST clearly follow the concern separation of a HTTP message:

  1. A resource identifierURI MUST be used to indicate identity only (related: Content Negotiation, Changes and Versioning)
  2. HTTP request method MUST be used to communicate the action semantics (intent and safety)
  3. HTTP response status code MUST be used to communicate the information about the result of the attempt to understand and satisfy the request
  4. HTTP message body MUST be used to transfer the message content
  5. HTTP message headers MUST be used to transfer the metadata about the message and its content
  6. URI query parameter SHOULD NOT be used to transfer metadata

Example 1

The rule

A resource identifierURI MUST be used to indicate identity only

implies there MUST NOT be an information about the media type or version of resource in the URI. For example URIs /greeting.json or /v2.1.3/greeting are illegal as they are not used for identification of a resource only but they convey the information about representation format and version.

Example 2

The rule

HTTP message body MUST be used to transfer the message content

implies an HTTP GET request MUST NOT use HTTP message body to identify the resource. For example a request:

GET /greeting HTTP/1.1
Content-Type: application/json
...


{
    "filter": "string"
    "depth": 3
}

is not acceptable (ignoring the fact that HTTP GET method shouldn't have the body). To express identity use URI and query parameters instead e.g. /greeting?filter=string&depth=3.


Keep things simple while designing by separating the concerns between the different parts of the request and response cycle. Keeping simple rules here allows for greater focus on larger and harder problems.

Requests and responses will be made to address a particular resource or collection. Use the path to indicate identity, the body to transfer the contents and headers to communicate metadata. Query params may be used as a means to pass header information also in edge cases, but headers are preferred as they are more flexible and can convey more diverse information.

Heroku HTTP API Design Guide