createRecurringJob

Creates a recurring Bulk Data Exchange Job and assigns it a recurringJobId. When you create a recurring job, you must include a recurrence interval, such as Daily, Weekly, Monthly, or Frequency In Minutes. Once a recurring job has been created, a separate job ID is created for each job that is created/executed. For example, if a job runs every hour, it will have a recurring job ID and each hourly job will have a jobId and file reference ID.



Back to top

Input Output Samples Change History
createRecurringJob Input

The box below lists all fields that could be included in the call request. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

See also Samples.

<?xml version="1.0" encoding="utf-8"?>
<createRecurringJobRequest xmlns="http://www.ebay.com/marketplace/services">
  <dailyRecurrence> DailyRecurrence 
    <timeOfDay> time </timeOfDay>
  </dailyRecurrence>
  <downloadJobType> token </downloadJobType>
  <frequencyInMinutes> int </frequencyInMinutes>
  <monthlyRecurrence> MonthlyRecurrence 
    <dayOfMonth> token </dayOfMonth>
    <timeOfDay> time </timeOfDay>
  </monthlyRecurrence>
  <UUID> string </UUID>
  <weeklyRecurrence> WeeklyRecurrence 
    <dayOfWeek> token </dayOfWeek>
    <timeOfDay> time </timeOfDay>
  </weeklyRecurrence>
</createRecurringJobRequest>
Argument Type Occurrence Meaning
dailyRecurrence DailyRecurrence Optional Optional element to specify a daily schedule for a recurring job.
dailyRecurrence.timeOfDay time Required Recurring Time for the job to run ex:08:00:00.000Z
downloadJobType token Required Specifies the report you want to download. Each Bulk Data Exchange job can only have one jobType per job. For instance, if you are downloading a SoldReport, it will only have pre-defined SoldReport data within the file.

Applicable values:
ActiveInventoryReport
A report that contains all of the active listings for a specific seller ID. The eBay servers read the credential information passed in by the seller's application to determine which seller's data to retrieve.
FeeSettlementReport
A report that contains all of the fees that you have incurred as invoices are generated by the eBay servers. This report gives large merchants the ability to look at their fees for many listings in one file.
SoldReport
Lists all items that have been sold by this seller (sold items that were submitted to the Large Merchant Service by the seller's application).

When an item is sold, the eBay application creates an 'order' for the seller. If only one item is sold, there is one order ID and one line item ID associated with the sale. However, if multiple items are sold as part of the same transaction, there is one order ID for the sale, and multiple line item IDs - one line item ID for each item sold.

Therefore, the Sold Report returns the order IDs and line item IDs for every order associated with the seller who is making the request. Sellers use this information to make inventory updates and start order fulfillment.

When orders have been fulfilled, the seller will probably want to remove them from the list of all orders that comes back every time they receive a SoldReport. To do this, they can acknowledge each order that has been fulfulled (using order ID or line item ID) by uploading a list of the fulfulled order information using an OrderAck request.

After you upload a data file with an OrderAck request, the orders (or line items within an order) will no longer appear in the SoldReport. (After you send the first OrderAck call, future SoldReports that you request will only contain unacknowledged orders and line items.)
frequencyInMinutes int Optional Use this element to specify job recurrence interval in minutes.
monthlyRecurrence MonthlyRecurrence Optional Optional element to specify a monthly schedule for a recurring job.
monthlyRecurrence.dayOfMonth token Required Allowed Values: Day_1, Day_2, Day_3, ...Day_28, Day_Last
monthlyRecurrence.timeOfDay time Required Recurring Time for the job to run ex:08:00:00.000Z
UUID string Required A Universally Unique Identifier (UUID) provided by the seller's application.
weeklyRecurrence WeeklyRecurrence Optional Optional element to specify a weekly schedule for a recurring job.
weeklyRecurrence.dayOfWeek token Required Allowed Values: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday
weeklyRecurrence.timeOfDay time Required Recurring Time for the job to run ex:08:00:00.000Z



Back to top

Input Output Samples Change History
createRecurringJob Output

The box below lists all fields that might be returned in the response. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

See also Samples.

<?xml version="1.0" encoding="utf-8"?>
<createRecurringJobResponse xmlns="http://www.ebay.com/marketplace/services">
  <!-- Standard Output Fields -->
  <ack> AckValue </ack>
  <errorMessage> ErrorMessage 
    <error> ErrorData 
      <category> ErrorCategory </category>
      <domain> string </domain>
      <errorId> long </errorId>
      <exceptionId> token </exceptionId>
      <message> string </message>
      <parameter name="string"> ErrorParameter (string) </parameter>
      <!-- ... more parameter nodes here ... -->
      <severity> ErrorSeverity </severity>
      <subdomain> string </subdomain>
    </error>
    <!-- ... more error nodes here ... -->
  </errorMessage>
  <timestamp> dateTime </timestamp>
  <version> string </version>
  <!-- Call-specific Output Fields -->
  <recurringJobId> string </recurringJobId>
</createRecurringJobResponse>
Return Value Type Occurrence Meaning
Standard Output Fields   [Jump to call-specific fields]
ack AckValue Always Returns the acknowledgement of the call success or failure.

Applicable values:

•   Failure

(out) 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.

•   PartialFailure

(out) Reserved for future use.

•   Success

(out) The request was processed successfully, but something occurred that may affect your application or the user.

•   Warning

(out) The request that triggered the error was processed successfully but with some warnings.
errorMessage ErrorMessage Conditionally Information for an error or warning that occurred when eBay processed the request.
errorMessage.error ErrorData Conditionally,
repeatable: [0..*]		 Details about a single error.
errorMessage.error.category ErrorCategory Conditionally There are three categories of errors: request errors, application errors, and system errors.

Applicable values:

•   Application

(out) 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.

•   Request

(out) 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.

•   System

(out) Indicates that an error has occurred on the eBay system side, such as a database or server down. An application 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.
errorMessage.error.domain string Conditionally Name of the domain upon which the error occurred.
Domains include:
Marketplace
A business or validation error occurred for the Bulk Data Exchange service.
SOA
An exception occurred in the Service Oriented Architecture (SOA) framework.
errorMessage.error.errorId long Conditionally 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.
errorMessage.error.exceptionId token Conditionally Unique identifier for an exception associated with an error.
errorMessage.error.message string Conditionally A detailed description of the condition that resulted in the error.
errorMessage.error.parameter ErrorParameter (string) Conditionally,
repeatable: [0..*]		 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.
errorMessage.error.parameter
  [ attribute name ]		 string Conditionally The name of the parameter in the get of parameter types returned within the error type.
errorMessage.error.severity ErrorSeverity 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.

Applicable values:

•   Error

(out) 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.

•   Warning

(out) 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.
errorMessage.error.subdomain string Conditionally Name of the subdomain upon which the error occurred.
Subdomains include:
BulkDataExchangeService
The error is specific to the BulkDataExchangeService service.
MarketplaceCommon
The error is common to all Marketplace services.
timestamp dateTime Always The data and time of the response.
version string Always The version of the schema that your WSDL is based on.
Call-specific Output Fields
recurringJobId string Always Recurring Job ID obtained by calling createRecurringJobRequest.



Back to top

Input Output Samples Change History
createRecurringJob Samples

New to making API calls? Please see Making an API Call.

Note: Some item IDs, user IDs, or other data in these samples might no longer be active on eBay. If necessary, you can substitute current eBay data in your requests.

Sample: Basic Call

Creates a recurring job for the Bulk Data Exchange service. Recurring jobs are most commonly used to automate report generation.

Description

User megaonlinemerchant creates a recurring ActiveInventoryReport that will run every week (frequency = 10080 minutes), so that she can check her active eBay inventory against the stock she has in her warehouse.

As a result of this call, megaonlinemerchant will be able to download an ActiveInventoryReport every week.

Input

In the following createRecurringJob request sample, you will see that you need a UUID (Universally Unique Identifier), the frequency in minutes that you want the job to generate, and the type of job you will be generating (such as SoldReport or ActiveInventoryReport). As a best practice, we recommend using a Universally Unique Identifier generator that uses a timestamp as part of the generation algorithm, so that the ID is always unique. The frequency for a SoldReport must not be more than two reports per hour, while the frequency for an ActiveInventoryReport must be not be more than one report per day. See Report Frequency Table for more information. 

XML format (HTTP POST). Also available are the .txt version of this XML and the SOAP equivalent.

<?xml version="1.0" encoding="utf-8"?>
<createRecurringJobRequest xmlns="http://www.ebay.com/marketplace/services">
  <UUID>d6e56ff0-a545-11dd-ad8b-0800200c9a66</UUID>
  <frequencyInMinutes>5040</frequencyInMinutes>
  <downloadJobType>ActiveInventoryReport</downloadJobType>
</createRecurringJobRequest>

Output

The response includes a Success or Failure acknowledgement, a timestamp, and the version number of the Bulk Data Exchange service. 

XML format. Also available are the .txt version of this XML and the SOAP equivalent.

<?xml version="1.0" encoding="utf-8"?>
<createRecurringJobResponse xmlns="http://www.ebay.com/marketplace/services">
  <ack>Success</ack>
  <version>1.0.0</version>
  <timestamp>2008-10-28T23:13:05.587Z</timestamp>
  <recurringJobId>5000000102</recurringJobId>
</createRecurringJobResponse>



Back to top

Input Output Samples Change History
createRecurringJob Change History
Version Description
1.0.0
2008-11-29
  • (added) New call

This document was generated with a customized version of the apireferencedocs tool.

© 2008–2009 eBay, Inc. All rights reserved. This documentation and the API may only be used in accordance with the eBay Developers Program and API License Agreement.