fix: remove unused webhook event variants - #129
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Greptile SummaryThis PR removes four webhook event variants that Request Network does not emit and aligns the public documentation with the 10 supported events.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains; the previously reported stale scoped-variant references have been removed from the current documentation. Important Files Changed
Reviews (3): Last reviewed commit: "fix: remove unused webhook event variant..." | Re-trigger Greptile |
MantisClone
force-pushed
the
fix/REQ-350-remove-unused-webhook-events
branch
from
August 21, 2026 22:37
c6195cf to
601be1a
Compare
MantisClone
marked this pull request as ready for review
August 21, 2026 22:40
This was referenced Aug 24, 2026
MantisClone
force-pushed
the
fix/REQ-350-remove-unused-webhook-events
branch
from
August 25, 2026 16:43
601be1a to
727f200
Compare
MantisClone
changed the base branch from
graphite-base/129
to
08-25-chore_add_webhook_payload_examples
August 25, 2026 16:43
rodrigopavezi
approved these changes
Aug 25, 2026
Contributor
Author
Merge activity
|
MantisClone
changed the base branch from
08-25-chore_add_webhook_payload_examples
to
graphite-base/129
August 25, 2026 17:12
MantisClone
added a commit
that referenced
this pull request
Aug 25, 2026
# Problem Yorvi (aka. Cheetah) needs current webhook payload examples in the main public documentation. The Client ID linking and KYT examples are only available in a separate orchestrator guide, while payment confirmation and Secure Payment Page examples are already on the main Webhooks page. [REQ-455](https://linear.app/requestnetwork/issue/REQ-455/mintlify-docs-add-current-cheetah-webhook-payload-examples) # Proposed Solution - Add the current `client_id.linked` payload example to the main Webhooks reference. - Add the current `kyt.screening.completed` payload example to the same reference. - Leave endpoint registration, event routing, and the existing orchestrator guide unchanged. # Considerations - This PR documents current payloads only. The broader Client ID/orchestrator delivery and identity guidance is in #130. - #129 stacks on this PR. # UAT 1. Open the [Mintlify preview](https://requestnetwork-08-25-chore-add-webhook-payload-examples.mintlify.site/api-reference/webhooks#payload-examples). 2. Confirm it includes examples for `client_id.linked` and `payment.confirmed`. 3. Confirm the [KYT screening payload](https://requestnetwork-08-25-chore-add-webhook-payload-examples.mintlify.site/api-reference/webhooks#kyt-screening-completed) includes `kyt.screening.completed`. 4. Confirm the [Secure Payment user-event payload](https://requestnetwork-08-25-chore-add-webhook-payload-examples.mintlify.site/api-reference/webhooks#secure-payment-user-event) remains available. 5. Confirm the existing payment-confirmation and Secure Payment Page examples remain unchanged.
MantisClone
force-pushed
the
fix/REQ-350-remove-unused-webhook-events
branch
from
August 25, 2026 17:13
727f200 to
9657432
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Problem
The public docs list four payment webhook variants that Request Network never emits. That can lead you to build handlers for notifications that will never arrive.
REQ-350
Proposed Solution
Considerations
UAT
payment.confirmed.*andpayment.partial.*variants are absent, and the catalog lists 10 supported events.