DaBRemService

CreateRemMessage

The following routes are available for this service:
All Verbs	/CreateRemMessage/{ClientKey}

**CreateRemMessage** Parameters:
Name	Parameter	Data Type	Required
ClientKey	path	string	No
AuthorizationID	query	string	No
RemAddressId	query	long	No
RemAttributesValues	query	RemAttributes	No

**RemAttributes** Parameters:
Name	Parameter	Data Type	Required
SubscriberId	form	long	No
Owner	form	string	No
FromAddress	form	string	No
ToAddresses	form	string	No
CcAddresses	form	string	No
Subject	form	string	No
BodyType	form	string	No
Body	form	string	No
AutoSignerYn	form	bool	No
TrMessageType	form	string	No

**CreateRemMessageResponse** Parameters:
Name	Parameter	Data Type	Required	Description
RemID	form	long	No

**BaseResponse** Parameters:
Name	Parameter	Data Type	Required
Result	form	bool	No
ErrorCode	form	int	No
ErrorMessage	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /CreateRemMessage/{ClientKey} HTTP/1.1 
Host: remservices.eyyubiye.bel.tr 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"ClientKey":"String","AuthorizationID":"String","RemAddressId":0,"RemAttributesValues":{"SubscriberId":0,"Owner":"String","FromAddress":"String","ToAddresses":"String","CcAddresses":"String","Subject":"String","BodyType":"String","Body":"String","AutoSignerYn":false,"TrMessageType":"String"}}

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

{"RemID":0,"Result":false,"ErrorCode":0,"ErrorMessage":"String"}