We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to add an extra header into the envelope to be signed?
Selling Partner API uses x-amz-access-token header, which is also required to be signed.
x-amz-access-token
https://developer-docs.amazon.com/amazon-shipping/docs/connecting-to-the-selling-partner-api#authorization-header
Authorization: AWS4-HMAC-SHA256 Credential=AKIAIHV6HIXXXXXXX/20201022/us-east-1/execute-api/aws4_request SignedHeaders=host;user-agent;x-amz-access-token;x-amz-date Signature=5d672d79c15b13162d9279b0855cfba6789a8edb4c82c400e06b5924aEXAMPLE
(I split it into lines for better readability)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there a way to add an extra header into the envelope to be signed?
Selling Partner API uses
x-amz-access-token
header, which is also required to be signed.https://developer-docs.amazon.com/amazon-shipping/docs/connecting-to-the-selling-partner-api#authorization-header
(I split it into lines for better readability)
The text was updated successfully, but these errors were encountered: