Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I agree with the 400 Bad Request response. </p> <p>For inspiration you could have a look at how Twitter (widely used JSON service) does this: <a href="https://dev.twitter.com/overview/api/response-codes" rel="nofollow noreferrer">https://dev.twitter.com/overview/api/response-codes</a></p> <h2> <code>Code</code> <code>Text</code> Description</h2> <ul> <li><code>200</code> <code>OK</code> - Success! </li> <li><code>304</code> <code>Not Modified</code> - There was no new data to return. </li> <li><code>400</code> <code>Bad Request</code> - The request was invalid or cannot be otherwise served. An accompanying error message will explain further. Requests without authentication are considered invalid and will yield this response. </li> <li><code>401</code> <code>Unauthorized</code> - Missing or incorrect authentication credentials. Also returned in other circumstances (for example, all calls to API v1 endpoints return 401). </li> <li><code>403</code> <code>Forbidden</code> - The request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why. This code is used when requests are being denied due to update limits . Other reasons for this status being returned are listed alongside the response codes in the table below. </li> <li><code>404</code> <code>Not Found</code> - The URI requested is invalid or the resource requested, such as a user, does not exists. Also returned when the requested format is not supported by the requested method. </li> <li><code>406</code> <code>Not Acceptable</code> - Returned when an invalid format is specified in the request. </li> <li><code>410</code> <code>Gone</code> - This resource is gone. Used to indicate that an API endpoint has been turned off. </li> <li><code>420</code> <code>Enhance Your Calm</code> Returned when an application is being rate limited . </li> <li><code>422</code> <code>Unprocessable Entity</code> - Returned when an image uploaded to POST account / update_profile_banner is unable to be processed. </li> <li><code>429</code> <code>Too Many Requests</code> - Returned when a request cannot be served due to the application’s rate limit having been exhausted for the resource. See Rate Limiting . </li> <li><code>500</code> <code>Internal Server Error</code> = Something is broken. Please post to the developer forums with additional details of your request, in case others are having similar issues. </li> <li><code>502</code> <code>Bad Gateway</code> - Twitter is down or being upgraded. </li> <li><code>503</code> <code>Service Unavailable</code> - The Twitter servers are up, but overloaded with requests. Try again later. </li> <li><code>504</code> <code>Gateway Timeout</code> - The Twitter servers are up, but the request couldn’t be serviced due to some failure within our stack. Try again later.</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload