[1] interagent/http-api-design ( ( 版)) https://github.com/interagent/http-api-design

[2] Platform API Reference | Heroku Dev Center ( ( 版)) https://devcenter.heroku.com/articles/platform-api-reference#clients

Accept: application/vnd.heroku+json; version=3
[3] interagent/http-api-design ( 版) https://github.com/interagent/http-api-design

You may consider optionally providing a way for clients to retrieve more verbose response, either via a query parameter (e.g. ?pretty=true) or via an Accept header param (e.g. Accept: application/vnd.heroku+json; version=3; indent=4;).

[4] Require Versioning in the Accepts Header · HTTP API Design (Wesley Beary著, ) https://geemus.gitbooks.io/http-api-design/content/en/foundations/require-versioning-in-the-accepts-header.html

It is best to provide version specification in the headers, with other metadata, using the Accept header with a custom content type, e.g.:

Accept: application/vnd.heroku+json; version=3

[5] Keep JSON minified in all responses · HTTP API Design (Wesley Beary著, ) https://geemus.gitbooks.io/http-api-design/content/en/responses/keep-json-minified-in-all-responses.html

You may consider optionally providing a way for clients to retrieve more verbose response, either via a query parameter (e.g. ?pretty=true) or via an Accept header param (e.g. Accept: application/vnd.heroku+json; version=3; indent=4;).

[6] Container Registry & Runtime (Docker Deploys) | Heroku Dev Center () https://devcenter.heroku.com/articles/container-registry-and-runtime

-H "Content-Type: application/json" \

-H "Accept: application/vnd.heroku+json; version=3.docker-releases"