<preclass="terminal">

$ curl https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy

$ curl'https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy'

</pre>

This should only be used in server to server scenarios. Don't leak your

see[events](http://developer.github.com/v3/activity/events/) for example.

<preclass="terminal">

$ curl https://api.github.com/user/repos?page=2&per_page=100

$ curl'https://api.github.com/user/repos?page=2&per_page=100'

</pre>

Note that page numbering is 1-based and that omitting the`?page`

secret in the query string.

<preclass="terminal">

$ curl -i https://api.github.com/users/whatever?client_id=xxxxxxxxxxxxxx&client_secret=yyyyyyyyyyyyyyyyyyyyy

$ curl -i'https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy'

HTTP/1.1 200 OK

Date: Mon, 01 Jul 2013 17:27:06 GMT

There's nothing you can do here as users are free to choose not to use

your application. More oftenthat not, users will just close the window

your application. More oftenthan not, users will just close the window

or press back in their browser, so it is likely that you'll never see

this error.

<%= headers 204 %>

In order for GitHub to send Webhook payloads to your service, your server needs to be accessible from the Internet. We also highly suggest using SSL so that we can send encrypted payloads over HTTPS.

GitHub will send along a few HTTP headers to differentiate between event types and payload identifiers.

Name | Description

-----|-----------|

`X-GitHub-Event` | The[event type](#events) that was triggered.

`X-GitHub-Delivery` | A[guid][guid] to identify the payload and event being sent.

`X-GitHub-Signature` | The value of this header is computed as the HMAC hex digest of the body, using the`secret` config option as the key.

GitHub can also serve as a[PubSubHubbub][pubsub] hub for all repositories.

``hub.secret``|`string` | A shared secret key that generates a SHA1 HMAC of the outgoing body content. You can verify a push came from GitHub by comparing the raw request body with the contents of the`X-Hub-Signature` header. You can see[our Ruby implementation][ruby-secret], or[the PubSubHubbub documentation][pshb-secret] for more details.

[guid]:http://en.wikipedia.org/wiki/Globally_unique_identifier

[pubsub]:http://code.google.com/p/pubsubhubbub/

[post-receive]:http://help.github.com/post-receive-hooks/

[ruby-secret]:https://github.com/github/github-services/blob/14f4da01ce29bc6a02427a9fbf37b08b141e81d9/lib/services/web.rb#L47-L50

[hub-signature]:https://github.com/github/github-services/blob/f3bb3dd780feb6318c42b2db064ed6d481b70a1f/lib/service/http_helper.rb#L77

[pshb-secret]:http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#authednotify

[events-url]:/webhooks/#events

[ping-event-url]:/webhooks/#ping-event

[ping-event-url]:/webhooks/#ping-event