2 Minute Read

Below are the Return Error responses for 75F APIs

The following all assume an Accept head with the value "text/zinc". 

  • Missing APIM subscription key ("Ocp-Apim-Subscription-Key" header)

{ "statusCode": 401, "message": "Access denied due to missing subscription key. Make sure to include a subscription key when making requests to an API." } 

  • Azure APIM subscription key invalid 

{ "statusCode": 401, "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription." } 

  • Invalid CCU token results in 401 with no response body 

Requesting data for points the user doesn't have permission to returns a 200 and an empty grid (hisReadMany) ver:"3.0" hisStart:2022-04-07T21:29:47.535524Z hisEnd:2022-04-07T21:29:47.535524Z empty

  • Sending a request to an unrecognized path returns a 404 

{ "statusCode": 404, "message": "Resource not found" } 

  • Sending a /read request that returns no entities results in 404 and an error grid 

ver:"3.0" err dis:"Requested entity not found" empty 

  • Sending malformed requests results in a 400 and an error grid 

ver:"3.0" err dis:"Invalid filter: "" empty

  • Sending a URL that is too long results in a 414 and an HTML response 




<TITLE>Request URL Too Long</TITLE> 

 <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"> 



<h2>Request URL Too Long</h2> <hr><p>HTTP Error 414. The requested URL is too long.</p>  









Please sign in to leave a comment.

Was this article helpful?

0 out of 0 found this helpful
Powered by Zendesk