You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Null values
JSON messages with null values are supported by web service calls and Blueriq as a Service.
| JSON Message | Domain schema | |
|---|---|---|
| BaaS request | Property value null | Property not required |
| BaaS response | Property absent | Property not required |
| Web service request | ||
| Web service response |
Incoming JSON messages containing properties with null values are allowed for non-required properties. When a property is specified as non-required
When a response to a REST JSON web service 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, so there won't be any null values in web service call requests.
Responses
Blueriq as a Service
HTTP status codes
When working with Blueriq as a Service (Baas) 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 header for an unsupported MIME type. |
| 500 | An unexpected exception occured while handling the request. |
Overview
Content Tools