[do not merge] CEXT-5381: Configure hook headers using the application context #457
+46
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oshmyheliuk
reviewed
Oct 21, 2025
src/pages/webhooks/hooks.md
Outdated
| Active: Yes | ||
| ``` | ||
|
|
||
| In this example, the `X-Custom-Header` from the incoming HTTP request to Commerce will be forwarded as a header in the webhook's request to the external system. |
There was a problem hiding this comment.
I would mention that this example can be used for passing through Authorization headers to solve authorization issues with webhooks.
oshmyheliuk
approved these changes
Oct 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request (PR) adds information on configuring hook headers using the application context.
Affected pages
Links to Magento Open Source code