Integrity & Signing
Headers carrying a digest or a signature over the message, so a recipient can prove it arrived as it was sent.
| Header | Providers | Status | |
|---|---|---|---|
| x-jws-signature | 35 | de-facto | regulated |
| Signature | 33 | permanent | regulated |
| Digest | 13 | obsoleted | regulated |
| Tpp-Signature-Certificate | 3 | vendor | regulated |
| Content-Digest | 3 | permanent | |
| Signature-Input | 2 | permanent | |
| Replay-Nonce | 2 | permanent | |
| Want-Repr-Digest | — | permanent | |
| Want-Digest | — | obsoleted | |
| Want-Content-Digest | — | permanent | |
| Unencoded-Digest | — | permanent | |
| Repr-Digest | — | permanent | |
| Detached-JWS | — | permanent | |
| Want-Unencoded-Digest | — | permanent |
All categories
Authentication Authorization & Scope Caching Conditional Requests & Concurrency Content Negotiation Representation Metadata Connection & Transport CORS Security Policy Privacy & Consent Rate Limiting & Quota Tracing & Correlation Idempotency & Reliability Versioning & Lifecycle Integrity & Signing Async & Long-Running Cost & Metering Agent & Bot Identity
Work with this as data
Every header here is available over the APIs.io API and to AI agents over MCP. HTTP Headers is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.