Using the v6.0 RestAPI, and trying to GET data from Spira in json-format, the API requires that the Content-Type header is set to application/json. Clearly, it should be the Accept header that should be conveyed with the application/json value. Example: curl --user : -H Accept: application/json https://spiraservice.net/Services/v6_0/RestService.svc/projects/9/releases returns a 400 Bad request error while: curl --user : -H Content-Type: application/json https://spiraservice.net/Services/v6_0/RestService.svc/projects/9/releases returns a 200 OK with the requested data. Why does it matter? Trying to send a GET request with a Content body (required to set the content-header) using a .NET HttpClient, throws: ProtocolViolationException {Cannot send a content-body with this verb-type.} Getting Microsoft to change this behavior is probably not possible, but the Spira API should correctly handle the Accept header instead of the Content-Type header here. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/2828.aspxthreadId=2828Björn Lundmark (bjorn@distributedmedical.com) Using the v6.0 RestAPI, and trying to GET data from Spira in json-format, the API requires that the Content-Type header is set to application/json. Clearly, it should be the Accept header that should be conveyed with the application/json value. Example: curl --user : -H Accept: application/json https://spiraservice.net/Services/v6_0/RestService.svc/projects/9/releases returns a 400 Bad request error while: curl --user : -H Content-Type: application/json https://spiraservice.net/Services/v6_0/RestService.svc/projects/9/releases returns a 200 OK with the requested data. Why does it matter? Trying to send a GET request with a Content body (required to set the content-header) using a .NET HttpClient, throws: ProtocolViolationException {Cannot send a content-body with this verb-type.} Getting Microsoft to change this behavior is probably not possible, but the Spira API should correctly handle the Accept header instead of the Content-Type header here. Thu, 13 Jul 2023 09:57:49 -04002023-07-13T10:24:11-04:00/Support/Forum/spirateam/issues-questions/2828.aspxmessageId=6158David J (adam.sandman+support@inflectra.com) It is because we are using a Microsoft WCF to implement the web service layer and we have to dynamically support both JSON and XML, so we need to use the Content-Type header to know which to use. So unfortunately were also limited by Microsoft as well ;-) Thu, 13 Jul 2023 10:24:11 -04002023-07-13T10:24:11-04:00/Support/Forum/spirateam/issues-questions/2828.aspx#reply6158