heilog.ch.Api

CreateCustomTreatmentRequest

The following routes are available for this service:
POST	/treatment/custom

**CreateCustomTreatmentRequest** Parameters:
Name	Parameter	Data Type	Required	Description
Treatment	body	CustomTreatmentDto	No

**CustomTreatmentDto** Parameters:
Name	Parameter	Data Type	Required
Id	form	long	No
IllnessId	form	long	No
EssenceId	form	long	No
TargetType	form	TargetType	No
EffectiveAspect	form	EffectiveAspect	No
Symptom	form	string	No

**TargetType** Enum:
Name	Value
Human	1
Animal	2

**EffectiveAspect** Enum:
Name	Value
UNSET	1
HOMEO	2
AROMATIC	3
MINERAL	4
PHYTO	5

**CreateCustomTreatmentResponse** Parameters:
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 .xml suffix or ?format=xml

HTTP + XML

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.test.exanic.ch 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<CreateCustomTreatmentRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/heilog.ch.Api.ServiceModel.Treatment">
  <Treatment xmlns:d2p1="http://schemas.datacontract.org/2004/07/heilog.ch.Api.Dto.Treatment">
    <d2p1:EffectiveAspect>UNSET</d2p1:EffectiveAspect>
    <d2p1:EssenceId>0</d2p1:EssenceId>
    <d2p1:Id>0</d2p1:Id>
    <d2p1:IllnessId>0</d2p1:IllnessId>
    <d2p1:Symptom>String</d2p1:Symptom>
    <d2p1:TargetType>Human</d2p1:TargetType>
  </Treatment>
</CreateCustomTreatmentRequest>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<CreateCustomTreatmentResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/heilog.ch.Api.ServiceModel.Treatment">
  <TreatmentId>0</TreatmentId>
</CreateCustomTreatmentResponse>