TFTP Web Services API

<back to all web services

FTPFirmwareUpdateSessionRequest

The following routes are available for this service:
POST/FTP/Sessionwill create a unique requestId for each firmware file
GET/FTP/Session/FTP/Session?requestIds={requestIds}&format=xml(requestId is separated by comma eg. 0f5b0cade06c43c984686bbea.bin,0f5b0cade06c43c984686bbeb.bin)
DELETE/FTP/Session/FTP/Session?uid={uid}&format=xml

To override the Content-type in your clients 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 /jsv/reply/FTPFirmwareUpdateSessionRequest HTTP/1.1 
Host: tftp-api.connect24.com 
Content-Type: text/jsv
Content-Length: length

{
	uid: String,
	FirmwareDeviceList: 
	[
		{
			FileName: String,
			UpdateOrder: 0,
			DisplayName: String,
			TranslatedDescription: String,
			EstimatedLocalUpdateTimeInMinutes: 0,
			Type: String,
			ImageFiles: 
			[
				{
					ImageFileID: String,
					ImageFileVer: String
				}
			],
			Version: String,
			Market: String,
			VersionToUpdate: String,
			GlassId: String,
			SoftwareVariant: String
		}
	],
	requestIds: String
}

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

{
	SessionFirmwareDevices: 
	[
		{
			RequestId: String,
			FileName: String,
			UpdateOrder: 0,
			DisplayName: String,
			TranslatedDescription: String,
			EstimatedLocalUpdateTimeInMinutes: 0,
			Type: String,
			ImageFiles: 
			[
				{
					ImageFileID: String,
					ImageFileVer: String
				}
			],
			Version: String,
			Market: String,
			VersionToUpdate: String,
			GlassId: String,
			SoftwareVariant: String
		}
	],
	OperationStatus: False,
	StatusCode: 0,
	StatusMessage: String,
	ExtendedStatusMessage: String
}