Tpp-Signature-Certificate
vendor
request
reached by regulation
2 spellings
Declared by 2 providers across 25 published specification files in the APIs.io network.
A count here is providers whose published contract declares this header — not
providers who send it. Response headers set at the edge rarely appear in an OpenAPI at all, so a low
number can measure documentation practice rather than deployment.
Spelled 2 ways
HTTP field names are case-insensitive (RFC 9110 §5.1), so every spelling below is the same header on the wire. A contract is not the wire: generated clients key off the string, and a developer reading two of these sees two different headers.
Tpp-Signature-CertificateTPP-Signature-Certificate
Reached by regulation
Basis: mandated.
The law, or a technical standard the law makes binding, names this header.
Only a credentialed caller can observe it in flight — the catalog can see a contract declare it, not a deployment honour it.
Carried by the berlin-group-nextgenpsd2 standard.
Providers declaring it (2)
tribe-payments triodos-bank-uk
Explore
All headers Integrity & Signing Guidance on headers.apievangelist.com