Transfers a data file to one of eBay's servers. After your application makes this call, it needs to make the Bulk Data Exchange 'StartUploadJob' call so the data can be processed.

Transfers a data file to one of eBay's servers.

samples This is an external identifier used by a service that interacts with the File Transfer Service. For instance, the Bulk Data Exchange Service uses a job ID as a primary identifier, so, if you're using the Bulk Data Exchange Service, enter the job ID as the taskReferenceId. uploadFile Yes A unique ID assigned to a file by the Bulk Data Exchange service when createUploadJobRequest or startDownloadJob is called. Pass the fileReferenceId into a File Transfer service uploadJobRequest or downloadJobRequest call. The File Transfer Service uses this identifier to keep track of the files that are uploaded or downloaded. uploadFile Yes Specifies the format of the file being uploaded. <dl> <dt> gzip </dt> <dd> It specifies that the file to be uploaded is in gzip format </dd> <dt> zip </dt> <dd> It specifies that the file to be uploaded is in zip format. </dd> </dl> uploadFile Yes The zipped report file that is encoded in Base64 Binary format and included in the request according to the SOAP MTOM standard. uploadFile Yes Downloads a file (typically a report) from eBay. <h3>Using downloadFile with the Bulk Data Exchange API</h3> If you are using Large Merchant Services, the most common uses of this call are to download responses to large-volume requests and to download reports. After you have uploaded a data file that includes requests (such as multiple AddFixedPriceItem requests), your seller or application will receive an email when a response is ready to download. After you receive this notification, you call downloadFile to retrieve the response. To get a report, you begin by using the Bulk Data Exchange API's startDownloadJob call, and then use startDownloadJob to start the report processing. The Bulk Data Exchange API assigns a jobId for your report and sends you (or the user) an email when the report is ready to download. After you receive this notification, your application can call downloadFile to download the report. <h3>Using downloadFile for Custom Item Specifics</h3> You can also use downloadFile to download recommendations for custom Item Specifics. This is a very large data set that can't be retrieved through a more traditional synchronous call. You do not use the Bulk Data Exchange API at all for this use case. (You also do not use uploadFile.) Instead, you call GetCategorySpecifics in the Trading API to obtain the necessary file and task reference IDs, and then pass them in the downloadFile call to retrieve the recommendations file. See <a href="http://developer.ebay.com/DevZone/XML/docs/Reference/eBay/GetCategorySpecifics.html#downloadFile">GetCategorySpecifics</a> for details.

Transfers the report information from one of eBay's servers.

samples This is ID is determimed by a service (or API) that interacts with the File Transfer API. For instance, the Bulk Data Exchange API uses a job ID as a primary identifier, so, if you're using the Bulk Data Exchange API, enter the job ID as the taskReferenceId. downloadFile Yes A unique Id assigned to a file. For example, the Bulk Data Exchange API assigns this ID to a file when createUploadJob or startDownloadJob is called and it creates the file. lt;br> Pass the fileReferenceId into a File Transfer API uploadJob or downloadJob call. The File Transfer API uses this identifier to keep track of the files that are uploaded or downloaded. downloadFile Yes Indicates the success or failure of transferring the data file to one of eBay's servers. Indicates the success or failure of transferring the report information to the seller's application. A zipped report file that is encoded in Base64 Binary format and included in the response according to the SOAP MTOM standard. downloadFile Always This is the base class for the request container for all service operations. Base response container for all service operations. Contains error information associated with the request. Indicates the success or failure of transferring data to eBay's servers. Always Information for an error or warning that occurred when eBay processed the request. Conditionally The version of the schema that your WSDL is based on. Always The date and time that the response was sent. Always Indicates whether the error is a severe error (causing the request to fail) or an informational error (a warning) that should be communicated to the user. The request was processed successfully, but something occurred that may affect your application or the user. The request that triggered the error was not processed successfully. When a serious application-level error occurs, the error is returned instead of the business data. The request that triggered the error was processed successfully but with some warnings. The request that triggered the error was processed successfully but there is some error in the application or data. ErrorMessage to indicate any Error/Warning that occurred as part of the service call. Runtime errors will not be reported here, but will be reported as SOAP errors. Details about a single error. Conditionally Error details. A unique code that identifies the particular error condition that occurred. Your application can use error codes as identifiers in your customized error-handling algorithms. Conditionally Name of the domain upon which the error occurred. <dl> <lh>Domains include:</lh> <dt> Marketplace </dt> <dd> A business or validation error occurred for the Merchandising Service. </dd> <dt> SOA </dt> <dd> An exception occurred in the Service Oriented Architecture (SOA) framework. </dd> </dl> Conditionally Indicates whether the error caused the request to fail (Error) or not (Warning). If the request fails and the source of the problem is within the application (such as a missing required element), please change the application before you retry the request. If the problem is due to end-user input data, please alert the end-user to the problem and provide the means for them to correct the data. Once the problem in the application or data is resolved, you can attempt to re- send the request to eBay. If the source of the problem is on eBay's side, you can retry the request as-is a reasonable number of times (eBay recommends twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, the request may be resent in its original form. When a warning occurs, the error is returned in addition to the business data. In this case, you do not need to retry the request (as the original request was successful). However, depending on the cause or nature of the warning, you might need to contact either the end user or eBay to effect a long term solution to the problem to prevent it from reoccurring in the future. Conditionally There are three categories of errors: request errors, application errors, and system errors. Conditionally A detailed description of the condition that resulted in the error. Conditionally Name of the subdomain upon which the error occurred. <dl> <lh>Subdomains include:</lh> <dt> Merchandising </dt> <dd> The error is specific to the Merchandising service. </dd> <dt> MarketplaceCommon </dt> <dd> The error is common to all Marketplace services. </dd> </dl> Conditionally Unique identifier for an exception associated with an error. Conditionally Some warning and error messages return one or more variables that contain contextual information about the error. This is often the field or value that triggered the error. Conditionally Contextual information associated with an error. The name of the parameter in the list of parameter types returned within the error type. Conditionally Indicates whether the error is a severe error (causing the request to fail) or an informational error (a warning) that should be communicated to the user. The request that triggered the error was not processed successfully. When a serious application-level error occurs, the error is returned instead of the business data. The request was processed successfully, but something occurred that may affect your application or the user. For example, eBay may have changed a value the user sent in. In this case, eBay returns a normal, successful response and also returns the warning. There are three categories of error: request errors, application errors, and system errors. Request and application errors are caused primarily by invalid data passed in the request. System errors are caused by application failures and cannot be corrected by changing request values. Indicates that an error has occurred on the eBay system side, such as a database or server outage. An application can retry the request a reasonable number of times (eBay recommends twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, the request may be resent in its original form. An error occurred due to a problem with the request, such as missing or invalid fields. The problem must be corrected before the request can be made again. If the problem is due to something in the application (such as a missing required field), the application must be changed. Once the problem in the application or data is resolved, resend the corrected request to eBay. An error occurred due to a problem with the request, such as invalid or missing data. The problem must be corrected before the request can be made again. If the problem is a result of end-user data, the application must alert the end-user to the problem and provide the means for the end-user to correct the data. Once the problem in the data is resolved, resend the request to eBay with the corrected data. The zipped report file that is encoded in Base64 Binary format and included in the request according to the SOAP MTOM standard. The size of the included zip file. This is the file that contains your Merchant Data API or Trading API requests or responses. The maximum size for this file is 15MB. When you use this with uploadFile, if you have a large call limit and you want to send more calls than would fit in a 15MB file, you will have to divide your data into multiple uploads. uploadFile Yes downloadFile Always The data in the attached file. When this is returned in downloadFile and you are working with Large Merchant Services or GetCategorySpecifics, the file is a .zip file. uploadFile Yes downloadFile Always 1.1.0