Betting.WebApi

<back to all web services

AddLocationDevice

Requires Authentication
The following routes are available for this service:
POST/cmd/locations/devices/add
AddLocationDevice Parameters:
NameParameterData TypeRequiredDescription
IdbodystringNo
DevicebodyDeviceNo
Device Parameters:
NameParameterData TypeRequiredDescription
IdformstringNo
NameformstringNo
IsActiveformboolNo
ProfileformDeviceProfileNo
IntegrationsDataformRecordDictionary<string, string>No
DeviceProfile Parameters:
NameParameterData TypeRequiredDescription
UsageModeformDeviceUsageModeNo
UserInterfaceformDeviceUserInterfaceNo
WalletformRefNo
ManagedByformDeviceManagement?No
DeviceUsageMode Enum:
NameValue
ClerkServiced0
Personal1
SelfService2
Unknown-1
DeviceUserInterface Enum:
NameValue
Tablet0
Kiosk1
Default2
Unknown-1
Ref Parameters:
NameParameterData TypeRequiredDescription
IdformstringYes
ValformstringYes
DeviceManagement Enum:
NameValue
Partner1
Platform2

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

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