-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
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
[WEBHOOK]: Initial integration #1392
Conversation
REBASED |
Update the specs options to include using header/path/body for the webhook authentication key. |
a040012
to
cb74855
Compare
beeef27
to
616af1d
Compare
@amadolid Tested this and I have one question What should the URL look like for the Otherwise, this works as expected, resolve the conflict and the comments and I can merge this. |
Here's the sample webhook using path as auth walker webhook {
can enter1 with `root entry {
report here;
}
class __specs__ {
has webhook: dict = {"type": "path", "name": "key"}, path: str = "/{key}";
}
} Here's how to call it curl -X 'POST' \
'http://localhost:8001/webhook/walker/webhook/676cf326532283bae2b574b5%3A1736237645%3AmnSMcWwdmdYD90rLyXUCBEDGFVHJEceR' \
-H 'accept: application/json' \
-d '' |
I see. We need to document this. Can you add one example each for each type (header/path/query/payload) just like what you did here and include it in the documentation? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to merge this one. I'd like someone to use this to validate it covers the common use case.
@ChrisIsKing i think you were trying to use webhook for a messaging platform integration right? Could you take this for a spin?
WEBHOOK
X-API-KEY
)CREATE WEBHOOK
WEBHOOK MANAGEMENT APIs
GENERATE API KEY
REQUEST
RESPONSE
GET API KEY
REQUEST
RESPONSE
EXTEND API KEY
REQUEST
RESPONSE
DELETE API KEY
REQUEST
RESPONSE