X-Amz-Target
Declared by 58 providers across 4412 published specification files in the APIs.io network.
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.
X-Amz-Targetx-amz-target
Providers declaring it (58)
amazon-app-runner amazon-codebuild amazon-codedeploy amazon-codepipeline amazon-codestar amazon-cognito amazon-comprehend amazon-compute-optimizer amazon-config amazon-device-farm amazon-direct-connect amazon-directory-service amazon-dms amazon-dynamodb amazon-ecr amazon-ecs amazon-eventbridge amazon-gamelift amazon-global-accelerator amazon-glue amazon-health-dashboard amazon-healthlake amazon-iam-identity-center amazon-iot-fleetwise amazon-kinesis amazon-managed-apache-flink amazon-mechanical-turk amazon-mediastore amazon-migration-hub amazon-network-firewall amazon-payment-cryptography amazon-private-ca amazon-proton amazon-route53-resolver amazon-sagemaker amazon-secrets-manager amazon-snow-family amazon-step-functions amazon-storage-gateway amazon-swf amazon-systems-manager amazon-textract amazon-timestream amazon-transcribe amazon-workmail amazon-workspaces aws-app-runner aws-codebuild aws-glue aws-healthlake aws-redshift aws-step-functions aws-waf dynamodb fargate kinesis macrometa scalable-systems
Explore
All headers Connection & Transport 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.