Questions about the API license agreement.

[ttt_34]

If this isn't the right place for this question, would someone help me find the correct place?

1. I was reading the API license agreement and one  point caught my eye. From the section on Public Display:

> eBay Content in a Public Display may not be co-mingled or combined with non-eBay Content. For example, all eBay Content in a Public Display must be visually isolated from third-party listings or other non-eBay information.

I would like to understand better what is and isn't allowed, and I have three questions about this:

1.1 What is considered "eBay content"? I imagine that pictures are, but my website doesn't contain any pictures, just text. If I have on my website prices and product titles, is that considered eBay content that I need to "not co-mingle"? What if I don't display product titles (for example, I could describe the product myself without using eBay's title) but still display price and link to eBay?

1.2 What is considered "visually isolated"?  For example, if I put on my website a list of prices and titles in a certain category, and some of those are links to eBay and some are links to other online shops, is that "co-mingling"? If so, what do I have to do to "visually isolate" the content? For example, if I add text [eBay] in front of eBay's title, is that enough to consider it visually isolated?

1.3 Is there some documentation with examples of things which are NOT allowed?

2. Elsewhere we're told that we need to implement a mechanism for user deletion:

> Note: All existing and new third-party developers integrated with eBay APIs via the eBay Developers Program are required to: 1) subscribe to eBay marketplace account deletion/closure notifications; or 2) follow the process to opt out of subscribing to these notifications if they do not store any eBay data for various reasons. If this is the case, the developer may apply for exemption from receiving eBay marketplace account deletion/closure notifications. For more information on opting out, see the Opting Out of eBay Marketplace Account Deletion/Closure Notifications section in this document.

I would like confirmation that the requirement to subscribing to account deletion notifications apply only to use cases that involve eBay's users. For example, my reading is that if I have a list of product titles and prices, and eBay's users never do any authentication on my website or otherwise provide me with any of their data, then I can opt-out. Is this correct? Or does the simple fact that I will be display eBay's listing titles require me to implement this feature, even there's no use for it in that case?

Best regards

John

[comics-scifi-collectibles]

@ttt_34   I am going to "phone a friend" .  @shipscript  is a fellow mentor that has API experience.  

[shipscript · Accepted solution]

Hi John, let me address the easy one first:

Marketplace Account Deletion.

If you do not have access to a user account (private data), and are only accessing publicly available data, then you can claim an exemption. You MUST complete the form, whether to participate or claim an exemption. eBay controls the visibility of "public" data, so you have no worries there.

If you have a developer account, this is where you would need to make the exemption declaration for account deletion.

https://developer.ebay.com/my/push?env=production&index=0 

As to your first question (Public Display), I currently see at least three types of API applications accessing eBay's public data:

1) One is the eBay Partner Network, which compensates members who display content on their own websites to bring buyers to the eBay site. Those would need to be standalone eBay widgets that clearly point to great deals on eBay - commingling with other sales platforms is not allowed within the widget.

2) Another is a developer-provided custom application. There is typically no intermingling with other sites.  I have such applications designed specifically for sellers.

3) Your question suggests the third use. I have encountered websites and user groups that focus on a selected product range, and then compare prices and point to where the items can be purchased. If editorial in nature, then there is no issue. If clickbait in nature, you will start to get into the gray area, where I don't have solid advice.

Because I think I may be the only developer who can respond to you on this particular forum, I will ask the moderators to move your post to the API forums. Unfortunately, there are few responders on the API forum and you may need to ask staff to respond.

[ttt_34]

ShipScript, this is really good info. Regarding the exemption, all clear, thank you 🙂

Regarding Public Display. I guess my use case is between 1 and 3. It's a bit of 3, since it's a website that focuses on price comparison within a niche that I know well. It's not clickbait in the sense that I show different products, their different characteristics, and different prices in different shops. If a user is interested he can click on the link to the shop, or not. All links are clearly marked as blue or purple underlined clickable text. Presumably users will choose the cheapest link for the product features they care about. I would like it to also be a bit of 1, as I would like to get an affiliate commission.

Do you know if there's an official process for getting some sort of representative to review and say "yes this is good" or "no, you need to do such and such to make it clear that these are links to eBay and not shop X"? If such a representative told me I need to mark my links with text like [link to eBay] in front or something I would be happy to that.

[shipscript]

https://developer.ebay.com/support/developer-account-support

I need information about the permitted uses of eBay's API

        eBay APIs are intended for eBay members (and developers acting on their behalf) to grow their buying and/or selling business on eBay.

        Sellers can use the API to manage end-to-end selling activities, from inventory management through fulfillment and feedback. Buyers can use the API to browse and search for items, manage watch lists, place bids and buy it now, and even complete checkout (if eligible).

        We typically do not permit other uses of eBay data.  We recommend that you review the eBay API License Agreement carefully before you develop your application.

Above is what eBay says about the API. This limited view really doesn't address the eBay Partner Network approach, which requires their widgets be marked as ads (this may address the no commingling aspect) and that prohibits various nefarious activities. Based on what is not allowed by EPN, one has to infer that bringing sales to eBay  falls within allowable guidelines. In that light, one could look at your editorial list of "where to buy" as a similar enhancement. I would definitely make it very clear to your readers where each link points. 

I don't know where you could reach out to eBay. We could ask developer_support@ebay  to respond to your question here on the forum, but he would likely just post a link back to the API agreement.

The only other way, that I know of,  to reach support is to purchase support hours to ask your question.

https://developer.ebay.com/my/support/tickets 

[ttt_34]

> This limited view really doesn't address the eBay Partner Network approach

You know what, thanks for spelling this out. It hadn't really sunk in that the "API permitted uses" and the "partner network code of conduct" aren't the same thing. I'll review the later carefully, but yes, I've already decided that I'll flag outgoing links as such.