WebService

ERAS2ClientNotificationRequest

**ERAS2ClientNotificationRequest** Parameters:
Name	Parameter	Data Type	Required
eras2_version	query	string	No
eras2_license	query	string	No
CallingOS	query	string	No
CallingOSArchitecture	query	string	No
LocalIP	query	string	No
CallingHost	query	string	No
CallingUser	query	string	No
CallingDomain	query	string	No

**ERAS2ClientNotificationResponse** Parameters:
Name	Parameter	Data Type	Required	Description
notifications	form	List<ERAS2ClientNotification>	No

**ERAS2ClientNotification** Parameters:
Name	Parameter	Data Type	Required
noteID	form	long	No
infotext	form	string	No
valid_from	form	DateTime	No
valid_to	form	DateTime?	No
valid_version	form	string	No
license	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 /json/reply/ERAS2ClientNotificationRequest HTTP/1.1 
Host: 52.142.207.43 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"eras2_version":"String","eras2_license":"String","CallingOS":"String","CallingOSArchitecture":"String","LocalIP":"String","CallingHost":"String","CallingUser":"String","CallingDomain":"String"}

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

{"notifications":[{"noteID":0,"infotext":"String","valid_from":"\/Date(-62135596800000-0000)\/","valid_to":"\/Date(-62135596800000-0000)\/","valid_version":"String","license":"String"}]}