Page History
Table of contents
| Table of Contents |
|---|
Web service call
Request examples
Null values etc.
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 | |||||
| 401 | |||||
| 404 | |||||
| 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. | 406 | |||
| 500 | An unexpected exception occured occurred while handling the BaaS request | 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 |
Overview
Content Tools