All error objects have resource and field properties so that your client

can tell what the problem is. There's also an error code to let you

know what is wrong with the field. These are the possible validation error

know what is wrong with the field. These are the possible validation error

codes:

missing

PUT

: Used for replacing resources or collections. For PUT requests

with no`body` attribute, be sure to set the`Content-Length` header to zero.

with no`body` attribute, be sure to set the`Content-Length` header to zero.

DELETE

: Used for deleting resources.

Requests that require authentication will return 404, instead of 403, in some places.

This is to prevent the accidental leakage of private repositories to unauthorized

users.

users.

X-RateLimit-Remaining: 4966

</pre>

You can[contact us](https://github.com/contact) to request white listed access for your application. We prefer sites that

You can also check your rate limit status without incurring an API hit.

<%= headers 200 %>

<%= json:rate => {:remaining => 4999,:limit => 5000} %>

Please[contact us](https://github.com/contact) to request white listed access for your application. We prefer sites that

setup OAuth applications for their users.

Here's a sample request sent from a browser hitting

`http://some-site.com`:

Any domain that is registered as an OAuth Application is accepted.

Here's a sample request for a browser hitting[Calendar About Nothing](http://calendaraboutnothing.com/):

This is what the CORS preflight request looks like: