Mercedes.Auth.API

Authorisation

The following routes are available for this service:
POST	/v1/authorisation

**Authorisation** Parameters:
Name	Parameter	Data Type	Required
GasUserId	body	string	No
ApplicationDotRole	body	List<string>	No
GEMSOutletId	body	List<string>	No
Application	body	string	No

**AuthorisationResponse** Parameters:
Name	Parameter	Data Type	Required
status	form	string	No
GasUserId	form	string	No
Application	form	string	No
Roles	form	List<string>	No
GSSNRetailerIds	form	List<string>	No
DefaultGSSNRetailerId	form	string	No
DefaultVehicleType	form	string	No
DefaultRole	form	string	No
DefaultRoleCount	form	int	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 /v1/authorisation HTTP/1.1 
Host: prod-api-auth-mb-dhc.rapp-customers.co.uk 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	GasUserId: String,
	ApplicationDotRole: 
	[
		String
	],
	GEMSOutletId: 
	[
		String
	],
	Application: String
}

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

{
	status: String,
	GasUserId: String,
	Application: String,
	Roles: 
	[
		String
	],
	GSSNRetailerIds: 
	[
		String
	],
	DefaultGSSNRetailerId: String,
	DefaultVehicleType: String,
	DefaultRole: String,
	DefaultRoleCount: 0
}