Betting.WebApi

AddLocationDevice

The following routes are available for this service:
POST	/cmd/locations/devices/add

**AddLocationDevice** Parameters:
Name	Parameter	Data Type	Required	Description
Id	body	string	No
Device	body	Device	No

**Device** Parameters:
Name	Parameter	Data Type	Required
Id	form	string	No
Name	form	string	No
IsActive	form	bool	No
Profile	form	DeviceProfile	No
IntegrationsData	form	RecordDictionary<string, string>	No

**DeviceProfile** Parameters:
Name	Parameter	Data Type	Required
UsageMode	form	DeviceUsageMode	No
UserInterface	form	DeviceUserInterface	No
Wallet	form	Ref	No
ManagedBy	form	DeviceManagement?	No

**DeviceUsageMode** Enum:
Name	Value
ClerkServiced	0
Personal	1
SelfService	2
Unknown	-1

**DeviceUserInterface** Enum:
Name	Value
Tablet	0
Kiosk	1
Default	2
Unknown	-1

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

**DeviceManagement** Enum:
Name	Value
Partner	1
Platform	2

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 /cmd/locations/devices/add HTTP/1.1 
Host: api.bettor.webhop.biz 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"id":"String","device":{"id":"String","name":"String","isActive":false,"profile":{"usageMode":0,"userInterface":0,"wallet":{"id":"String","val":"String"},"managedBy":0},"integrationsData":{"String":"String"}}}

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

{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}