filter :enterprise_only_filter

filter :not_enterprise_filter

**UPDATE (2015-06-10):** As [announced on June 10][2015-06-10-update], these changes will become an official part of GitHub API v3 on June 24. (This post originally announced that these changes would come to GitHub API v3 on February 24.)

Last month, we [released a preview][org-permissions-preview] of several API changes related to managing organization members and repositories. Today, we're finalizing these changes. This new functionality is now stable and suitable for production use. If your application relies on any of the affected functionality (described below), be sure to **update your code before June 24** to account for these changes.

Starting today, we're offering a migration period allowing applications to opt in to these changes (as described below). On June 24, these changes will become official parts of the GitHub API v3. At that time, these changes will apply to all API consumers.

[2015-06-10-update]: /changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/

kind: change

title: Repository redirects are coming to API v3 in July

created_at: 2015-05-26

author_name: jasonrudolph

Last month, we announced the [upcoming repository redirect behavior for the API][original announcement], and we made it available for developers to preview. Starting **July 21, 2015**, the API will automatically provide these redirects for all API consumers.

To learn more about repository redirects and how they will benefit your applications, be sure to check out the [original announcement][].

To start enjoying repository redirects right away, just provide the following custom [media type][] in the `Accept` header:

application/vnd.github.quicksilver-preview+json

Thanks to everyone that tried out this enhancement during the preview period.

As always, if you have any questions, please [get in touch][contact]. We love hearing from you.

[media type]: /v3/media/

[original announcement]: /changes/2015-04-17-preview-repository-redirects/

[contact]: https://github.com/contact?form%5Bsubject%5D=API+Repository+Redirects

kind: change

title: Breaking changes to organization permissions coming on June 24

created_at: 2015-06-10

author_name: jakeboxer

Back in January, we [encouraged developers to update their applications][org-permissions-finalization] to prepare for [upcoming API changes][org-permissions-preview] related to managing organization members and repositories. In order to support the upcoming [improvements to organization permissions][direct-org-membership-blog-post], these changes will become official parts of GitHub API v3 on **June 24**.

If your application relies on any of the affected functionality (described below), be sure to **update your code before June 24** to account for these changes.

If your application uses any of the following APIs, then you are affected by this change:

- APIs for managing your organization's admins through the Owners team

- The [List your repositories][list-your-repos] API

- The [List your organizations][list-your-organizations] API

- The [List user organizations][list-user-organizations] API

If your application uses these APIs, we urge you to update your application as soon as possible. (Read [December's announcement][org-permissions-preview] for full details on the changes.)

In January, we [announced a migration period][org-permissions-finalization] allowing API consumers to opt in to these changes. If you haven't already opted in to these changes, you still do so as described below. On June 24, these changes will become official parts of GitHub API v3. At that time, these changes will apply to all API consumers.

During these final days of the migration period, you can opt in to these changes using the following custom media type in the `Accept` header:

application/vnd.github.moondragon+json

We want to make these updates as smooth as possible for everyone, and we hope that the migration period gives you flexibility to adopt these changes on your own schedule. If you have any questions or feedback, please [get in touch with us][contact]!

[org-permissions-finalization]: /changes/2015-01-07-prepare-for-organization-permissions-changes/

[org-permissions-preview]: /changes/2014-12-08-organization-permissions-api-preview/

[direct-org-membership-blog-post]: https://github.com/blog/2020-improved-organization-permissions/

[list-your-repos]: /v3/repos/#list-your-repositories

[list-user-organizations]: /v3/orgs/#list-user-organizations

[list-your-organizations]: /v3/orgs/#list-your-organizations

[contact]: https://github.com/contact?form[subject]=Organization+Permissions+API

kind: change

title: GitHub Pages' A Records Added to Meta API

created_at: 2015-06-11

author_name: leereilly

The [Meta API](/v3/meta/) now includes the A record IP addresses for [GitHub Pages](https://pages.github.com/).

<pre class="terminal">

$ curl https://api.github.com/meta

</pre>

<pre><code class="language-javascript">

{

"verifiable_password_authentication": true,

"github_services_sha": "23c6105183b626cf74c045f6d53af7a178bfdb4c",

"hooks": [

"192.30.252.0/22"

],

"git": [

"192.30.252.0/22"

],

"pages": [

"192.30.252.153/32",

"192.30.252.154/32"

]

}

</code></pre>

These IP addresses are used to [configure A records with your DNS provider for GitHub Pages](https://help.github.com/articles/tips-for-configuring-an-a-record-with-your-dns-provider/). These addresses have changed a few times in the past. This API always provides the current addresses so that you can automate the process of keeping your DNS records up to date.

If you have any questions, please [get in touch](https://github.com/contact?form%5Bsubject%5D=GitHub+Pages+A+Records+Added+to+API). We’ll be happy to help.

kind: change

title: List all organizations

created_at: 2015-06-17

author_name: keavy

We've added a [new API method](/v3/orgs#list-all-organizations) to list all organizations:

<pre class="terminal">

$ curl https://api.github.com/organizations

[

{

"login": "github",

"id": 9919,

"url": "https://api.github.com/orgs/github",

"repos_url": "https://api.github.com/orgs/github/repos",

"events_url": "https://api.github.com/orgs/github/events",

"members_url": "https://api.github.com/orgs/github/members{/member}",

"public_members_url": "https://api.github.com/orgs/github/public_members{/member}",

"avatar_url": "https://avatars.githubusercontent.com/u/9919?v=3",

"description": "GitHub, the company."

},

...

]

</pre>

As always, if you have any questions or feedback, please [drop us a line][contact].

[contact]: https://github.com/contact?form[subject]=API+-+Listing+Organizations

kind: change

title: API enhancements for working with organization permissions

created_at: 2015-06-24

author_name: jakeboxer

We're introducing several enhancements to allow API developers to take advantage of the [improved organization permissions][dotcom-blog-post] that we are rolling out. Learn about these enhancements and how you can try them out below.

Since we're rolling out the [improved organization permissions][dotcom-blog-post] improvements slowly, these enhancements will only apply to certain organizations at first. Most of these enhancements will degrade gracefully (returning an empty array or something similar) if used on an organization that doesn't support improved organization permissions yet. Check the documentation for your specific API to see if errors are possible.

In our improved permissions system, a team no longer has a single permission that applies to all of its repositories. Instead, each repository is added to a team with its own permission. For example, an organization could use a single team to grant pull access to one repository, push access to a second, and admin access to a third.

The team APIs now support this more granular notion of permissions:

- The [Add team repository][add-team-repo] API accepts a `permission` parameter, so that you can specify whether a team should grant `pull`, `push`, or `admin` access on a given repository.

- In the [List team repositories][list-team-repos] and [Check if a team manages a repository][get-team-repo] API, the response includes a `permissions` attribute, indicating whether the team grants `pull`, `push`, or `admin` access on each repository.

- The `permission` parameter in the [Create team][create-team] and [Edit team][edit-team] APIs is deprecated. Since teams can grant a different permission on each repository, this parameter no longer dictates what permission a team grants on all of its repositories. Instead, it dictates the default permission that the [Add team repository][add-team-repo] API will use for requests where no `permission` parameter is specified.

We now allow you to modify the privacy level of your teams. A "secret" team can only be seen by organization owners and people who are members of that team (which is how all teams have worked historically), while a "closed" team is visible to every member of the organization (which makes it easier to use [@mentions][team-mentions] throughout your organization).

The team APIs now support this new team privacy concept:

- The [Create team][create-team] and [Edit team][edit-team] APIs accept a `privacy` parameter, so that you can specify whether a team should be `secret` or `closed`.

- All team resources in the API now include a `privacy` attribute, indicating whether the team is `secret` or `closed`.

We've added the ability for you to delegate team maintenance to non-owners, reducing the workload for your organization's owners. You can now promote a non-owner member of a team to be a "maintainer" of that team. A maintainer can add and remove team members and change the team's title and description.

The team membership APIs now support this new team maintainer concept:

- The [Add team membership][add-team-membership] API accepts a `role` parameter, so that you can specify whether a given team member should be a `maintainer` or a regular `member`.

- The [List team members][list-team-members] API accepts an optional `role` parameter, allowing you to fetch only `maintainer`s or only regular `member`s.

- In the [Get team membership][get-team-membership] and [Add team membership][add-team-membership] APIs, the response includes a `role` attribute, indicating whether a user is a `maintainer` or a regular `member` of the team.

For more information on our improved team permissions, check out our [documentation][understanding-team-permissions].

The organization [Members list][org-members-list] API now accepts a `role` parameter, so that you can request to see only the owners (or non-owners) of your organization.

We now allow you to add collaborators directly to organization-owned repositories, just like we always have for user-owned repositories.

The collaborator APIs now support organization-owned repositories:

- The [Add user as a collaborator][add-collab] API works for organization-owned repositories. We've also added a `permission` parameter to it (currently valid for organization-owned repositories only), so that you can specify what level of access the collaborator should have on the repository.

- In the [List collaborators][list-collabs] API, the response includes a `permissions` attribute describing the permissions that each collaborator has on your organization's repositories.

Starting today, these API enhancements are available for developers to preview. At the end of the preview period, these enhancements will become official components of the GitHub API.

While these enhancements are in their preview period, you'll need to provide the following [custom media type][custom-media-types] in the `Accept` header:

application/vnd.github.ironman-preview+json

During the preview period, we may change aspects of these enhancements. If we do, we will announce the changes on the developer blog, but we will not provide any advance notice.

We would love to hear your thoughts on these enhancements. If you have any questions or feedback, please [get in touch with us][contact]!

[dotcom-blog-post]: https://github.com/blog/2020-improved-organization-permissions

[understanding-team-permissions]: https://help.github.com/articles/improved-organization-permissions/#understanding-team-permissions

[create-team]: /v3/orgs/teams/#create-team

[edit-team]: /v3/orgs/teams/#edit-team

[list-team-members]: /v3/orgs/teams/#list-team-members

[get-team-membership]: /v3/orgs/teams/#get-team-membership

[add-team-membership]: /v3/orgs/teams/#add-team-membership

[list-team-repos]: /v3/orgs/teams/#list-team-repos

[get-team-repo]: /v3/orgs/teams/#get-team-repo

[add-team-repo]: /v3/orgs/teams/#add-team-repo

[org-members-list]: /v3/orgs/members/#members-list

[org-public-members-list]: /v3/orgs/members/#public-members-list

[list-collabs]: /v3/repos/collaborators/#list

[add-collab]: /v3/repos/collaborators/#add-collaborator

[contact]: https://github.com/contact?form[subject]=Organization+Permissions+API

[team-mentions]: https://github.com/blog/1121-introducing-team-mentions

[custom-media-types]: /v3/media/

kind: change

title: Breaking changes to organization permissions are now official

created_at: 2015-06-24

author_name: jakeboxer

As [promised earlier this month][notice], the [API changes][api-changes] related to managing organization members and repositories are now official parts of the GitHub API.

During the migration period, you needed to [provide a custom media type in the `Accept` header][migration-period] to opt-in to the changes. Now that the migration period has ended, you no longer need to specify this custom [media type][media-types].

If you have any questions or feedback, please [get in touch with us][contact]!

[notice]: /changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24

[api-changes]: /changes/2014-12-08-organization-permissions-api-preview/

[contact]: https://github.com/contact?form[subject]=Organization+Permissions+API

[media-types]: /v3/media

[migration-period]: /changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/#migration-period

kind: change

title: Licenses API update

created_at: 2015-06-24

author_name: mislav

We are expanding the [Licenses API](/v3/licenses) to make it more useful for auditing license usage across all repositories owned by a user or organization.

Before, license information was only returned for an individual repository:

GET /repos/github/hubot

Now, license information will also be included in reponses from endpoints that list multiple repositories, such as [List organization repositories](/v3/repos/#list-organization-repositories):

GET /orgs/github/repos

As before, to access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:

application/vnd.github.drax-preview+json

For more information, see the [Licenses API documentation](/v3/licenses/), and if you have any questions or feedback, please [let us know](https://github.com/contact?form%5Bsubject%5D=Licenses+API).

Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user]:

Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user] to initialize our API client: