Antel API

SealDetailsRequest

The following routes are available for this service:
POST	/stock/seal/details

**SealDetailsRequest** Parameters:
Name	Parameter	Data Type	Required	Description
SealId	body	int	No

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

**SealDetailsResponse** Parameters:
Name	Parameter	Data Type	Required
PrincipalName	form	string	No
UpliftNumber	form	string	No
OperatorName	form	string	No
OutletName	form	string	No
UpliftDate	form	string	No
SealNumber	form	string	No
CurrentWeight	form	string	No
TargetWeight	form	string	No
HasWeightIssue	form	bool	No
BucketName	form	string	No
ClaimNumbers	form	List<string>	No
JoinedClaimNumbers	form	string	No
SealImages	form	List<FileDataItem>	No
OrderHistory	form	List<SealOrderHistoryItem>	No
MovementHistory	form	List<SealMovementHistoryItem>	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	No

**FileDataItem** Parameters:
Name	Parameter	Data Type	Required
FileName	form	string	No
FileUrl	form	string	No
ThumbnailUrl	form	string	No
FileId	form	Guid	No
ThumbnailId	form	Guid	No
LinkId	form	int	No
CreatedDate	form	DateTime	No

**SealOrderHistoryItem** Parameters:
Name	Parameter	Data Type	Required
CreatedDate	form	string	No
OrderId	form	int	No
OrderNumber	form	string	No
OrderRequestingOperator	form	string	No

**SealMovementHistoryItem** Parameters:
Name	Parameter	Data Type	Required
Id	form	long	No
EventDateTime	form	string	No
ActionUserName	form	string	No
ScannedDepotName	form	string	No
AssignedBucketName	form	string	No
AssignedOrderNumber	form	string	No
AssignedOperatorName	form	string	No
OrderDriverName	form	string	No
OrderDriverCompanyName	form	string	No
OrderDriverLicensePlate	form	string	No
TargetWeight	form	double	No
CurrentWeight	form	double	No
HadWeightIssue	form	bool	No
HadUnknownUplift	form	bool	No
WasPaused	form	bool	No
PausedWasAwaitingAuth	form	bool	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 /stock/seal/details HTTP/1.1 
Host: antel.api.dev.86degrees.com 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	sealId: 0,
	apiKey: String,
	latitude: 0,
	longitude: 0
}

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

{
	principalName: String,
	upliftNumber: String,
	operatorName: String,
	outletName: String,
	upliftDate: String,
	sealNumber: String,
	currentWeight: String,
	targetWeight: String,
	hasWeightIssue: False,
	bucketName: String,
	claimNumbers: 
	[
		String
	],
	joinedClaimNumbers: String,
	sealImages: 
	[
		{
			fileName: String,
			fileUrl: String,
			thumbnailUrl: String,
			linkId: 0,
			createdDate: 0001-01-01
		}
	],
	orderHistory: 
	[
		{
			createdDate: String,
			orderId: 0,
			orderNumber: String,
			orderRequestingOperator: String
		}
	],
	movementHistory: 
	[
		{
			id: 0,
			eventDateTime: String,
			actionUserName: String,
			scannedDepotName: String,
			assignedBucketName: String,
			assignedOrderNumber: String,
			assignedOperatorName: String,
			orderDriverName: String,
			orderDriverCompanyName: String,
			orderDriverLicensePlate: String,
			targetWeight: 0,
			currentWeight: 0,
			hadWeightIssue: False,
			hadUnknownUplift: False,
			wasPaused: False,
			pausedWasAwaitingAuth: False
		}
	],
	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
		}
	}
}