Betting.WebApi

RegisterOrganization

The following routes are available for this service:
POST	/cmd/organizations

**RegisterOrganization** Parameters:
Name	Parameter	Data Type	Required
Id	body	string	No
Name	body	string	No
Address	body	Address	No
Locale	body	Locale	No
IntegrationsData	body	RecordDictionary<string, string>	No
WinningsExpirationPolicy	body	WinningsExpirationPolicy	No
Nature	body	OrganizationNature?	No
Integrations	body	OrganizationIntegrations	No
PayoutPolicy	body	PayoutPolicy	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

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

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

**Locale** Parameters:
Name	Parameter	Data Type	Required
TimeZone	form	Ref	No
Currency	form	Ref	No
Language	form	Ref	No

**WinningsExpirationPolicy** Parameters:
Name	Parameter	Data Type	Required	Description
Enabled	form	bool	No
Interval	form	TimeSpan	No

**OrganizationNature** Enum:
Name	Value
FirstParty	1
Partner	2

**OrganizationIntegrations** Parameters:
Name	Parameter	Data Type	Required	Description
FirstParty	form	IntegrationInstance	No
Partner	form	IntegrationInstance	No

**IntegrationInstance** Parameters:
Name	Parameter	Data Type	Required
Id	form	string	No
IntegrationId	form	string	No
Wallet	form	IntegrationConnection	No
PartnerApi	form	IntegrationConnection	No
SlipForwardingEnabled	form	bool	No

**IntegrationConnection** Parameters:
Name	Parameter	Data Type	Required	Description
Url	form	string	No
CredentialsRef	form	string	No

**PayoutPolicy** Parameters:
Name	Parameter	Data Type	Required	Description
SelfService	form	WalletPayoutMode	No
Personal	form	WalletPayoutMode	No

**WalletPayoutMode** Enum:
Name	Value
RealTime	0
BatchPayout	1

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

{
	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
		}
	},
	locale: 
	{
		timeZone: 
		{
			id: String,
			val: String
		},
		currency: 
		{
			id: String,
			val: String
		},
		language: 
		{
			id: String,
			val: String
		}
	},
	integrationsData: 
	{
		String: String
	},
	winningsExpirationPolicy: 
	{
		enabled: False,
		interval: PT0S
	},
	nature: 0,
	integrations: 
	{
		firstParty: 
		{
			id: String,
			integrationId: String,
			wallet: 
			{
				url: String,
				credentialsRef: String
			},
			partnerApi: 
			{
				url: String,
				credentialsRef: String
			},
			slipForwardingEnabled: False
		},
		partner: 
		{
			id: String,
			integrationId: String,
			wallet: 
			{
				url: String,
				credentialsRef: String
			},
			partnerApi: 
			{
				url: String,
				credentialsRef: String
			},
			slipForwardingEnabled: False
		}
	},
	payoutPolicy: 
	{
		selfService: 0,
		personal: 0
	}
}

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
	}
}