| POST | /treatment/custom |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Treatment | body | CustomTreatmentDto | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | long | No | |
| IllnessId | form | long | No | |
| EssenceId | form | long | No | |
| TargetType | form | TargetType | No | |
| EffectiveAspect | form | EffectiveAspect | No | |
| Symptom | form | string | No |
| Name | Value | |
|---|---|---|
| Human | 1 | |
| Animal | 2 |
| Name | Value | |
|---|---|---|
| UNSET | 1 | |
| HOMEO | 2 | |
| AROMATIC | 3 | |
| MINERAL | 4 | |
| PHYTO | 5 |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| TreatmentId | form | long | 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 /treatment/custom HTTP/1.1
Host: heidak-api.build.exanic.ch
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
treatment:
{
id: 0,
illnessId: 0,
essenceId: 0,
targetType: 1,
effectiveAspect: 1,
symptom: String
}
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
treatmentId: 0
}