The[Repository Commits API](/v3/repos/commits/) now supports an additional approach for paginating[commit lists](/v3/repos/commits/#list-commits-on-a-repository). As of today, this endpoint supports the "standard"[`page` and`per_page` parameters](/v3/#pagination) for controlling pagination. This API now uses these parameters by default when constructing[page links](/v3/#pagination).

This new approach improves the reliability of this endpoint, which on rare occasions skipped some commits during pagination. This enhancement also increases the overall consistency of the API, as all endpoints now paginate resource lists the same way.

The old way of paginating, using`top`,`last_sha`, and`per_page` parameters, is still supported in API v3, but it will be removed in the[next major version of the API](https://developer.github.com/v3/versions/#v3-deprecations). API clients that are manually constructing URLs for pages should be modified to use the new parameters. Even better, API clients shouldn't construct URLs for pages manually, but should use[page links provided by the`Link` header](/guides/traversing-with-pagination/) in API responses.

Since we're developing locally for our tutorial, let's set it to`http://localhost:4567/payload`.

We'll explain why in the[Configuring Your Server](/webhooks/configuring/) docs.

Webhooks can deliver various[media types](/v3/media/) as defined by the GitHub API.

Choose the one that best fits your needs. For this tutorial, the default format is fine.

Webhooks can be delivered using different content types:

- The`application/json` content type will deliver the JSON payload directly as the body of the POST.

- The`application/x-www-form-urlencoded` content type will send the JSON payload as a form parameter

called "payload".

Choose the one that best fits your needs. For this tutorial, the default content type of

`application/json` is fine.