OData endpoint Http status codes
Aplica-se a: CRM 2015 on-prem, CRM Online
Http status codes returned by the REST endpoint are described in the following table. The status codes follow RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1.
Status Code | Text | Cause |
---|---|---|
200 |
OK |
The request is served. |
400 |
Bad Request |
The request could not be parsed successfully because of a syntactically or semantically incorrect URI. |
401 |
Unauthorized |
Authentication is required and has not been provided. |
403 |
Forbidden |
User does not have privileges to access the entity |
404 |
Record Not Found |
The record does not exist for the given query. |
405 |
Method Not Allowed |
A request cannot be used for this record. |
406 |
Not Acceptable |
The requested format specified in the accept header cannot be satisfied for the entity/entity container/entity set. |
413 |
Request Entity Too Large |
The request attempts to set too much data, or the requested range contains too many rows, returned data is too big. |
500 |
Internal Server Error |
Internal Error |
503 |
Service Unavailable |
Service Unavailable |
Consulte também
Referência
OData endpoint Http status codes
Conceitos
Usar o ponto de extremidade do OData com os recursos da Web JScript e Ajax
Usar o ponto de extremidade do OData com os recursos da Web
Executar operações de dados básicas usando o ponto de extremidade OData
Microsoft Dynamics CRM 2015 and Microsoft Dynamics CRM Online
Send comments about this topic to Microsoft.
© 2014 Microsoft Corporation. All rights reserved.