| POST | /api/configuration/validate |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Schema | body | string | No | |
| Json | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Errors | body | IList<ValidationError> | No | |
| Valid | body | bool | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Message | body | string | No | |
| LineNumber | body | int | No | |
| LinePosition | body | int | No | |
| Path | body | string | No | |
| Value | body | Object | No | |
| Schema | body | JSchema | No | |
| SchemaId | body | Uri | No | |
| SchemaBaseUri | body | Uri | No | |
| ErrorType | body | ErrorType | No | |
| ChildErrors | body | IList<ValidationError> | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /jsv/reply/ValidateRequest HTTP/1.1
Host: elm.alertsense.com
Content-Type: text/jsv
Content-Length: length
{
Schema: String,
Json: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
Valid: False
}