Betting.WebApi

GetSSDWalletProfile

The following routes are available for this service:
All Verbs	/qry/integrations/wallet/ssd

**GetSSDWalletProfile** Parameters:
Name	Parameter	Data Type	Required
DeviceId	query	string	No
SessionId	query	string	No
Data	query	RecordDictionary<string, string>	No

**SSDWalletProfile** Parameters:
Name	Parameter	Data Type	Required
Id	form	string	No
Device	form	Ref	No
Location	form	DeviceLocation	No

**Ref** Parameters:
Name	Parameter	Data Type	Required	Description
Id	form	string	Yes
Val	form	string	Yes

**DeviceLocation** Parameters:
Name	Parameter	Data Type	Required
Id	form	string	No
Name	form	string	No
Address	form	Address	No
Data	form	RecordDictionary<string, string>	No
TaxationAuthorityId	form	string	No

**Address** Parameters:
Name	Parameter	Data Type	Required
Street	form	string	Yes
City	form	string	Yes
State	form	string	Yes
PostalCode	form	string	Yes
Country	form	Ref	Yes
GPS	form	GPSCoordinates	Yes
Data	form	RecordDictionary<string, string>	Yes

**GPSCoordinates** Parameters:
Name	Parameter	Data Type	Required	Description
Lat	form	double	No
Lng	form	double	No

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

HTTP + JSV

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

POST /qry/integrations/wallet/ssd HTTP/1.1 
Host: api.sbbet.ath.cx 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	deviceId: String,
	sessionId: String,
	data: 
	{
		String: String
	}
}

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

{
	id: String,
	device: 
	{
		id: String,
		val: String
	},
	location: 
	{
		id: String,
		name: String,
		address: 
		{
			street: String,
			city: String,
			state: String,
			postalCode: String,
			country: 
			{
				id: String,
				val: String
			},
			gps: 
			{
				lat: 0,
				lng: 0
			},
			data: 
			{
				String: String
			}
		},
		data: 
		{
			String: String
		},
		taxationAuthorityId: String
	}
}