This repository was archived by the owner on Nov 1, 2017. It is now read-only.
- Notifications
You must be signed in to change notification settings - Fork1.1k
Clarify differences between Events API and webhooks#631
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
The `repository` and `sender` fields are not present in the Events API payloads (but are present in webhook deliveries). This notes that difference (which was previously indicated to be structurally identical JSON to the literal webhook examples except where noted).
Member
kdaigle commentedAug 17, 2015
Sorry for the delay in getting to your PR. 😢 I'm going to merge this to help clarify the difference between the Events API and our webhooks. 👍 |
kdaigle added a commit that referenced this pull requestAug 17, 2015
Clarify differences between Events API and webhooks
hubot added a commit that referenced this pull requestOct 9, 2015
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Labels
None yet
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.
I'd assumed that the name under "Event name" was used in the
typefield of the event object but I was wrong. There is a hint that the camel-cased variant is used on the Events page in the form of"type": "Event"but it's best to be explicit, anyway. Anyone who uses the API will notice immediately, anyway.