Antel Merchandiser App API

UpliftRequestAuthRequest

The following routes are available for this service:
POST	/upliftrequest/auth

**UpliftRequestAuthRequest** Parameters:
Name	Parameter	Data Type	Required
UpliftRequestOnDeviceId	body	Guid	No
OutletId	body	int	No
PrincipalId	body	int	No
TotalValue	body	decimal	No
TotalUnits	body	double	No
Region	body	string	Yes
Channel	body	string	Yes
Products	body	List<UpliftRequestProductData>	Yes

**ApiServiceRequest** Parameters:
Name	Parameter	Data Type	Required	Description
ApiKey	form	string	Yes	The API Key required for authentication
Latitude	form	double	No	Latitude of the user making this request
Longitude	form	double	No	Longitude of the user making this request

**UpliftRequestProductData** Parameters:
Name	Parameter	Data Type	Required
Id	form	Guid	No
UpliftRequestProductId	form	int	No
ProductId	form	int	No
PrincipalId	form	int	No
UnitPrice	form	decimal	No
Name	form	string	Yes
Category	form	string	Yes
UnitBarcode	form	string	Yes
UnitSize	form	string	Yes
UnitWeight	form	decimal	No
Code	form	string	Yes
Images	form	List<Object>	Yes
Quantity	form	double	No
Value	form	decimal	No
ProductionDate	form	string	Yes
ExpiryDate	form	string	Yes
BatchCode	form	string	Yes
Seal	form	SealData	Yes
SerialNumber	form	string	Yes
StockStatusId	form	int	No
PrincipalLogoUrl	form	string	Yes
PrincipalName	form	string	Yes
StockStatusName	form	string	Yes
StockStatusColor	form	string	Yes
UnitOfMeasureId	form	int	No

**Seal** Parameters:
Name	Parameter	Data Type	Required	Description
Number	form	string	No
Weight	form	double	No

**UpliftRequestAuthRequestResponse** Parameters:
Name	Parameter	Data Type	Required	Description
UpliftRequestAuthRequestId	form	Guid	No

**ApiServiceResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Description	form	string	Yes	Information about the response.
Heading	form	string	Yes	Heading or summary of the response.
WasSuccessful	form	boolean	Yes	Did the intended operation for this response complete successfully?
ResponseStatus	form	ResponseStatus	Yes

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 /upliftrequest/auth HTTP/1.1 
Host: returnit-api-dev.happen.zone 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	OutletId: 0,
	PrincipalId: 0,
	TotalValue: 0,
	TotalUnits: 0,
	Region: String,
	Channel: String,
	Products: 
	[
		{
			UpliftRequestProductId: 0,
			ProductId: 0,
			PrincipalId: 0,
			UnitPrice: 0,
			Name: String,
			Category: String,
			UnitBarcode: String,
			UnitSize: String,
			UnitWeight: 0,
			Code: String,
			Images: 
			[
				{
					
				}
			],
			Quantity: 0,
			Value: 0,
			ProductionDate: String,
			ExpiryDate: String,
			BatchCode: String,
			Seal: 
			{
				Number: String,
				Weight: 0
			},
			SerialNumber: String,
			StockStatusId: 0,
			PrincipalLogoUrl: String,
			PrincipalName: String,
			StockStatusName: String,
			StockStatusColor: String,
			UnitOfMeasureId: 0
		}
	],
	ApiKey: String,
	Latitude: 0,
	Longitude: 0
}

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

{
	Description: String,
	Heading: String,
	WasSuccessful: False,
	ResponseStatus: 
	{
		ErrorCode: String,
		Message: String,
		StackTrace: String,
		Errors: 
		[
			{
				ErrorCode: String,
				FieldName: String,
				Message: String,
				Meta: 
				{
					String: String
				}
			}
		],
		Meta: 
		{
			String: String
		}
	}
}