Page History
Table of contents
Table of Contents |
---|
Web service call
Null values
When a response to a REST JSON call contains properties with null values these properties will be handled as non-existent properties. This means that null values are only accepted for properties that are specified as non-required in the response domain schema. Non-required properties on request domain schemas are not present in the actual request that the web service call creates.
Blueriq as a Service
HTTP status codes
When working with Blueriq as a Service (BaasBaaS) there are several status HTTP status codes that can be expected in the response.
Response code | Description |
---|---|
200 | OK |
400 | The request could not be deserialized. |
401 | A non-accessible flow is requested. |
404 | An unknown web service is requested. |
406 | The request contains an Accept accept header for an unsupported MIME type. |
500 | An unexpected exception occured occurred while handling the request. |
Non-required properties
JSON messages with null values are supported by web service calls and Blueriq as a Service.
The following table shows all situations regarding a non-required property (as modelled in the domain schema in Studio) which is not set (value UNKNOWN):
JSON message | |
---|---|
BaaS request | Property absent or property value null |
BaaS response | Property absent |
Web service request | Property absent |
Web service response | Property absent or property value null |