openapi: 3.0.0 info: title: eBay Account Advertising_eligibility Traffic_report API description: The Account API gives sellers the ability to configure their eBay seller accounts, including the seller's policies (eBay business policies and seller-defined custom policies), opt in and out of eBay seller programs, configure sales tax tables, and get account information.

For details on the availability of the methods in this API, see Account API requirements and restrictions. contact: name: eBay Inc, license: name: eBay API License Agreement url: https://go.developer.ebay.com/api-license-agreement version: v1.9.2 servers: - url: https://api.ebay.com{basePath} description: Production variables: basePath: default: /sell/account/v1 tags: - name: Traffic_report paths: /traffic_report: get: tags: - Traffic_report description: This method returns a report that details the user traffic received by a seller's listings.

A traffic report gives sellers the ability to review how often their listings appeared on eBay, how many times their listings are viewed, and how many purchases were made. The report also returns the report's start and end dates, and the date the information was last updated.

For more information, see Traffic report details operationId: getTrafficReport parameters: - name: dimension in: query description: 'This query parameter specifies the dimension, or "attribute," that is applied to the report metric.

Valid values: DAY or LISTING

Examples ' required: false schema: type: string - name: filter in: query description: 'This query parameter refines the information returned in the traffic report.

Note: URL encode all the values you supply in the filter parameter. See URL encoding query parameter values as described in URL parameters.

Configure the following properties of the filter parameter to tune the traffic report to your needs:
Example filter parameter
The following example shows how to configure the filter parameter with the marketplace_ids and date_range filters:

filter=marketplace_ids:{EBAY_US},date_range:[20170601..20170828]

Encoding this portion of the query parameter sample yields:

filter=marketplace_ids:%7BEBAY_US%7D,date_range:%5B20230601..20230828%5D


See samples for additional examples. For implementation help, refer to eBay API documentation at https://developer.ebay.com/api-docs/sell/analytics/types/csb:FilterField' required: false schema: type: string - name: metric in: query description: 'This query parameter specifies the metrics you want covered in the report.

Note: Unlike names for parameters and enumerated values, metric values are not case sensitive.

Valid values:Specify a comma-separated list of the metrics to include them in the report. See Using different metric parameters for more information including detailed metric descriptions and localized names.' required: false schema: type: string - name: sort in: query description: 'This query parameter sorts the report on the specified metric.

You can only specify a single metric in the sort parameter and the specified metric must be included in the configuration of the report''s metric parameter.

Sorting is helpful when you want to review how a specific metric is performing, such as the CLICK_THROUGH_RATE.

Most reports can be sorted in ascending or descending order. Precede the value of a descending-order request with a minus sign ("-"), for example: sort=-CLICK_THROUGH_RATE.

Note: There are a couple of constraints on sorting the report by different metrics: For implementation help, refer to eBay API documentation at https://developer.ebay.com/api-docs/sell/analytics/types/csb:SortField' required: false schema: type: string responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/Report' '400': description: Bad Request x-response-codes: errors: '50001': domain: API_ANALYTICS category: REQUEST description: Invalid dimension specified. For help, see the documentation. '50002': domain: API_ANALYTICS category: REQUEST description: Invalid metric {metricName} specified. For help, see the documentation. '50003': domain: API_ANALYTICS category: REQUEST description: Invalid date range. End date must be before or equal to start date. '50004': domain: API_ANALYTICS category: REQUEST description: Invalid date range. Start date must be before or equal to end date. '50005': domain: API_ANALYTICS category: REQUEST description: No filter is specified, which is required. For help, see the documentation. '50006': domain: API_ANALYTICS category: REQUEST description: The sort field value {sortField} is not supported. '50008': domain: API_ANALYTICS category: REQUEST description: The call requires at least one metric. For help, see the documentation. '50009': domain: API_ANALYTICS category: REQUEST description: The call requires at least one URI query parameter. For help, see the documentation. '50013': domain: API_ANALYTICS category: REQUEST description: Invalid date range format - Start Date. The format is yyyyMMdd. '50014': domain: API_ANALYTICS category: REQUEST description: Invalid date range format - End Date. The format is yyyyMMdd. '50018': domain: API_ANALYTICS category: REQUEST description: Neither the start date nor the end date can be in the future. '50021': domain: API_ANALYTICS category: REQUEST description: Invalid filter field {filterField} specified. '50022': domain: API_ANALYTICS category: REQUEST description: Specify at least one marketplace ID. '50023': domain: API_ANALYTICS category: REQUEST description: The marketplace ID {marketplaceId} is not supported by this call. For help, see the documentation. '50024': domain: API_ANALYTICS category: REQUEST description: The marketplace ID {marketplaceId} is not valid. '50025': domain: API_ANALYTICS category: REQUEST description: The start date is too far in the past. The start date must be less than or equal to {maxStartDateInThePast}. '50026': domain: API_ANALYTICS category: REQUEST description: The date range is too long. The date range must be less than or equal to {maxDateWindow}. '50027': domain: API_ANALYTICS category: REQUEST description: The 'listing_id' value is empty. '50028': domain: API_ANALYTICS category: REQUEST description: The maximum number of listing IDs has been exceeded. The maximum number of listing IDs is {maxListingIdsNumber}. '50029': domain: API_ANALYTICS category: REQUEST description: Invalid listing ID {listingId}. '50030': domain: API_ANALYTICS category: REQUEST description: Data for the listing ID {listingId} could not be found. '50031': domain: API_ANALYTICS category: REQUEST description: Date range is required. '50033': domain: API_ANALYTICS category: REQUEST description: Invalid date range filter format {invalidDateRangeFilter}. '50034': domain: API_ANALYTICS category: REQUEST description: Invalid listing ids filter format {invalidListingIdsFilter}. '50035': domain: API_ANALYTICS category: REQUEST description: Requested sort field is not part of the list of metrics requested. '50036': domain: API_ANALYTICS category: REQUEST description: '{sortOrder} sort order is not supported for {sortField} metric.' '50037': domain: API_ANALYTICS category: REQUEST description: The Metric {metricName} does not have data available for the requested date range. '50600': domain: API_ANALYTICS category: REQUEST description: Data for the listing Ids {delayedListingIds} is not yet updated to {endDate} '500': description: Internal Server Error x-response-codes: errors: '50032': domain: API_ANALYTICS category: APPLICATION description: We are unable to process data for accounts, like this one, which have listed in more than a few thousand leaf categories in the past couple years. '50050': domain: API_ANALYTICS category: APPLICATION description: We are doing some maintenance and cannot show all your information right now. We are still tracking everything, and you will see your updated stats soon. '50500': domain: API_ANALYTICS category: APPLICATION description: Internal server error. Wait a few minutes and try the call again. If error persists contact the eBay Developer Program. security: - api_auth: - https://api.ebay.com/oauth/api_scope/sell.analytics.readonly components: schemas: Metadata: type: object properties: metadataHeader: description: The container that returns the dimensionKeys and metrics headers for the report. $ref: '#/components/schemas/MetadataHeader' metadataRecords: type: array description: A list of the individual report records. items: $ref: '#/components/schemas/MetadataRecord' description: Type the defines the metadata information of the report. This includes the headers and the individual metadata records. Report: type: object properties: dimensionMetadata: type: array description: A complex type containing the header of the report and the type of data containted in the rows of the report. items: $ref: '#/components/schemas/Metadata' endDate: type: string description: '

The time stamp is formatted as an ISO 8601 string, which is based on the 24-hour Universal Coordinated Time (UTC) clock.

If you specify an end date that is beyond the lastUpdatedDate value, eBay returns a report that contains data only up to the lastUpdateDate date.

Format: [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss].[sss]Z
Example: 2018-08-20T07:09:00.000Z' header: description: A complex type containing the header for the report. $ref: '#/components/schemas/Header' lastUpdatedDate: type: string description: The date and time, in ISO 8601 format, that indicates the last time the data returned in the report was updated. records: type: array description: A complex type containing the individual data records for the traffic report. items: $ref: '#/components/schemas/Record' startDate: type: string description: The start date of the date range used to calculate the report, in ISO 8601 format. warnings: type: array description: An array of any process errors or warnings that were generated during the processing of the call processing. items: $ref: '#/components/schemas/Error' description: The complex type that defines that defines the report. Value: type: object properties: applicable: type: boolean description: 'If set to true, this flag indicates the value in the value field is valid as computed.

A value of false indicates one or more of the values used to calculate the value was invalid. The occurrence of this is a rare, however consider this case: suppose a buyer navigates to a View Item page at 11:59 pm (the end of the day) and purchases the item at 12:05am the next day. In this case, the item would have been purchased with 0 views for the day.' value: type: object description: The value of the report data. description: A complex type that contains a value, plus the veracity of that value. ErrorParameter: type: object properties: name: type: string description: Name of the entity that threw the error. value: type: string description: A description of the error. description: A complex type that defines an error and error message. MetadataHeader: type: object properties: key: type: string description: 'The key value used for the report.

For example: "key": "LISTING_ID"' metadataKeys: type: array description: 'The list of dimension key values used for the report header. Each list element contains the key name, its data type, and its localized name.

For example:

"metadataKeys": [
  "key": "LISTING_TITLE",
  "localizedName": "Listing title",
  "dataType": "STRING"

' items: $ref: '#/components/schemas/Definition' description: Type that defines the metadata header fields. Record: type: object properties: dimensionValues: type: array description: A list where each element contains either the string DAY (if the dimension is DAY), or the listing ID for which the record's metric data is computed. A second array member, applicable, is always true for dimension values. items: $ref: '#/components/schemas/Value' metricValues: type: array description: A list where each element contains a value field that indicates the record's value for the metric. Each element also contains an applicable field that indicates the veracity of the computed value.

Note that there are no metric names or IDs associated with the values returned in this array. The metadata to which these values relate can be found in the key values in metadataKeys. The order of the metric values in this array equals the order of the key values in metadataHeader. items: $ref: '#/components/schemas/Value' description: Type that defines the fields of the individual record of the report. Definition: type: object properties: dataType: type: string description: Indicates the data type of the returned dimension. For example, if the dimension is day, the data type is DATE. For implementation help, refer to eBay API documentation key: type: string description: The value the dimension or metric parameter as submitted in the request. localizedName: type: string description: The localized name of the metric or dimension (translated into the language specified in the Accept-Language HTTP request header). For example, if Accept-Language is set to de-DE, the value "day" in the dimension container is returned as "tag", and a metric of TRANSACTION is returned as "Transaktionsanzahl". description: A complex type that defines a dimension key and metrics in a traffic report. Header: type: object properties: dimensionKeys: type: array description: A list of the dimension or metric keys returned in the report. The values for each are is returned in the associated key fields. items: $ref: '#/components/schemas/Definition' metrics: type: array description: The list of metrics returned in the report. The values for each are is returned in the associated key fields. items: $ref: '#/components/schemas/Definition' description: Type that defines the headers for the dimension keys and metrics returned in the report. Error: type: object properties: category: type: string description: Identifies whether the error was in the REQUEST or happened when running the APPLICATION. domain: type: string description: The primary system where the error occurred. This is relevant for application errors. For Analytics errors, it always has the value API_ANALYTICS. errorId: type: integer description: A positive integer that uniquely identifies the specific error condition that occurred. Your application can use error codes as identifiers in your customized error-handling algorithms. Traffic report error IDs range from 50001 to 50500. format: int32 inputRefIds: type: array description: Identifies specific request elements associated with the error, if any. inputRefId's response is format specific. For JSON, use JSONPath notation. items: type: string longMessage: type: string description: A more detailed explanation of the error than given in the message error field. message: type: string description: Information on how to correct the problem, in the end user's terms and language where applicable. Its value is at most 50 characters long. If applicable, the value is localized in the end user's requested locale. outputRefIds: type: array description: Identifies specific response elements associated with the error, if any. Path format is the same as inputRefId. items: type: string parameters: type: array description: This optional list of name/value pairs that contain context-specific ErrorParameter objects, with each item in the list being a parameter (or input field name) that caused an error condition. Each ErrorParameter object consists of two fields, a name and a value. items: $ref: '#/components/schemas/ErrorParameter' subdomain: type: string description: If present, indicates which subsystem in which the error occurred. description: Type that defines the fields that can be returned in an error. MetadataRecord: type: object properties: metadataValues: type: array description: A list of data in a row returned in the traffic report. The data in each of the cells match the labels in headers of the report. items: $ref: '#/components/schemas/Value' value: description: 'The value of the key on which the report is based.

For example, if the key is the listing ID, the value of this container could be:

"value": {
  "value": "142133954229",
  "applicable": true
}
' $ref: '#/components/schemas/Value' description: A complex type that defines the data records returned in the report. securitySchemes: api_auth: type: oauth2 description: The security definitions for this API. Please check individual operations for applicable scopes. flows: authorizationCode: authorizationUrl: https://auth.ebay.com/oauth2/authorize tokenUrl: https://api.ebay.com/identity/v1/oauth2/token scopes: https://api.ebay.com/oauth/api_scope/sell.account.readonly: View your account settings https://api.ebay.com/oauth/api_scope/sell.account: View and manage your account settings