You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 1, 2017. It is now read-only.
Copy file name to clipboardExpand all lines: content/v3/orgs.md
+16-1Lines changed: 16 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,22 @@ List organizations for the authenticated user.
13
13
14
14
###OAuth scope requirements
15
15
16
-
When using[OAuth](/v3/oauth/#scopes), authorizations must include`user` scope or`read:org` scope.
16
+
Currently, OAuth requests always receive the user's[public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership), regardless of the OAuth scopes associated with the request. If the OAuth authorization has`user` or`read:org` scope, the response also includes private organization memberships.
17
+
18
+
With the new Organization Permissions API (described below), this method will only return organizations that your authorization allows you to operate on in some way (e.g., you can list teams with`read:org` scope, you can publicize your organization membership with`user` scope, etc.). Therefore, this API will require at least`user` or`read:org` scope. OAuth requests with insufficient scope will receive a`403 Forbidden` response.
19
+
20
+
<divclass="alert">
21
+
<p>
22
+
The Organization Permissions API is currently available for developers to preview.
23
+
During the preview period, the API may change without notice.
24
+
Please see the <a href="/changes/2014-12-08-organization-permissions-api-preview/">blog post</a> for full details.
25
+
</p>
26
+
27
+
<p>
28
+
To access the API during the preview period, you must provide a custom <a href="/v3/media">media type</a> in the <code>Accept</code> header: