x-client-id
Declared by 53 providers across 1176 published specification files in the APIs.io network.
Spelled 4 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.
x-client-idX-Client-IdX-CLIENT-IDX-Client-ID
Providers declaring it (53)
airwallex aldermore att b3 bank-of-ireland-uk bank-of-scotland blockaid bmo bud-co cashfree channel99 chargetrip chase-uk citizens-financial-group cofactr coutts coventry-building-society cynergy-bank egym epa fabric-com first-direct gb-bank gsma hampden-and-co hometrack ikea intelycare investec jp-morgan-chase kroo kyber-network lloyds-banking-group mesh mesh-connect monument-bank netomi nexla open-banking-uk openenvoy oura paragon-bank parseflow plug recognise-bank santander-uk secure-trust-bank shawbrook-bank tandem-bank telkomsel thirdweb tribe-payments visa
Explore
All headers Authentication Guidance on headers.apievangelist.com
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.