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.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,8 +120,19 @@ already\_exists
120
120
can happen in resources that must have some unique key (such as Label
121
121
names).
122
122
123
-
If resources have custom validation errors, they will be documented with
124
-
the resource.
123
+
If resources have custom validation errors, they will be documented with the resource.
124
+
125
+
##HTTP Redirects
126
+
127
+
API v3 uses HTTP redirection where appropriate. Clients should assume that any request may result in a redirection. Receiving an HTTP redirection is*not* an error and clients should follow that redirect. Redirect responses will have a`Location` header field which contains the URI of the resource to which the client should repeat the requests.
128
+
129
+
301
130
+
: Permanent redirection. The URI you used to make the request has be superseded by the one specified in the`Location` header field. This and all future requests to this resource should be directed the new URI.
131
+
132
+
302, 307
133
+
: Temporary redirection. The request should be repeated verbatim to the URI specified in the`Location` header field but clients should continue to use the original URI for future requests.
134
+
135
+
Other redirection status codes may be used in accordance with the HTTP 1.1 spec.
125
136
126
137
##HTTP Verbs
127
138
@@ -185,7 +196,7 @@ users.
185
196
##Pagination
186
197
187
198
Requests that return multiple items will be paginated to 30 items by
188
-
default. You can specify further pages with the`?page` parameter.For some
199
+
default. You can specify further pages with the`?page` parameter. For some
189
200
resources, you can also set a custom page size up to 100 with the`?per_page` parameter.
190
201
Note that for technical reasons not all endpoints respect the`?per_page` parameter,
191
202
see[events](http://developer.github.com/v3/events/) for example.