Request-Id:

[1] interagent/http-api-design ( (2014-05-30 01:49:47 +09:00 版)) <https://github.com/interagent/http-api-design>

[2] Platform API Reference | Heroku Dev Center ( (2014-10-08 12:32:11 +09:00 版)) <https://devcenter.heroku.com/articles/platform-api-reference#request-id>

[3] Platform API Reference | Heroku Dev Center (2015-03-06 08:15:16 +09:00 版) <https://devcenter.heroku.com/articles/platform-api-reference#request-id>

Each API response contains a unique request id in the Request-Id header to facilitate tracking. When reporting issues, providing this value makes it easier to pinpoint problems and provide solutions more quickly.

[4] Stripe API Reference (2015-08-29 17:39:46 +09:00 版) <https://stripe.com/docs/api#idempotent_requests>

Each API request has an associated request identifier. You can find this in the response headers, under Request-Id.

[5] Provide Request-Ids for Introspection · HTTP API Design (Wesley Beary著, 2017-02-10 22:07:15 +09:00) <https://geemus.gitbooks.io/http-api-design/content/en/foundations/provide-request-ids-for-introspection.html>

Include a Request-Id header in each API response, populated with a UUID value. By logging these values on the client, server and any backing services, it provides a mechanism to trace, diagnose and debug requests.