Betting.WebApi

GetUserNotifications

The following routes are available for this service:
All Verbs	/qry/users/notifications

**GetUserNotifications** Parameters:
Name	Parameter	Data Type	Required	Description
Id	query	string	No

**UserNotifications** Parameters:
Name	Parameter	Data Type	Required
Id	form	string	No
N	form	int	No
S	form	int	No
I	form	int	No
W	form	int	No
E	form	int	No
Notifications	form	Dictionary<string, UserNotification>	No

**UserNotification** Parameters:
Name	Parameter	Data Type	Required
Id	form	string	No
Notification	form	Notification	No
DispatchedAt	form	DateTime	No

**Notification** Parameters:
Name	Parameter	Data Type	Required
Severity	form	Severity	No
Type	form	NotificationType	No
Data	form	RecordDictionary<string, string>	No

**Severity** Enum:
Name	Value
Success	0
Info	1
Warning	2
Error	3

**NotificationType** Enum:
Name	Value
Default	0
SlipDeliveryConfirmationRequest	1
SlipDeliveryIssueResolved	2

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

HTTP + OTHER

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

POST /qry/users/notifications HTTP/1.1 
Host: api.sbbet.ath.cx 
Accept: text/jsonl
Content-Type: text/jsonl
Content-Length: length

{"id":"String"}

HTTP/1.1 200 OK
Content-Type: text/jsonl
Content-Length: length

{"id":"String","n":1,"s":1,"i":0,"w":0,"e":0,"notifications":{"String":{"id":"String","notification":{"severity":0,"type":0,"data":{"String":"String"}},"dispatchedAt":"0001-01-01T00:00:00.0000000Z"}}}