question

helios825 avatar image
0 Likes"
helios825 asked

Finding/Shopping API Using https

It was just brought to my attention that the Finding API, Shopping API, and perhaps other legacy API families use https: endpoints. Historically it was just http (non-TLS/SSL). I see https: in several of the docs examples. Does anyone know when they changed this? I've read all eBay Dev blog posts for years now and don't recall that change. It's a good change, and I'm glad it occurred. And I suppose at some point they'll terminate the non-TLS http: endpoints, so I'm just generally wondering what kind of timeline we might be seeing there. Thanks.
httpsslendpointtls
10 |600 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

clickimusprime avatar image
0 Likes"
clickimusprime answered
As least as far back as 2016. They did the TLS 1.2 update then and TLS was already supported https://ebaydts.com/eBayKBDetails?KBid=5073
10 |600 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

helios825 avatar image
0 Likes"
helios825 answered
Ok, thanks. I'll need to convert over my calls soon. I'm guessing it's as simple as adding an 's' to the endpoint, but I do some POSTing, and not yet sure if curl requires some special SSL params.
10 |600 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

clickimusprime avatar image
0 Likes"
clickimusprime answered
Watch those response times. in can take up to 10 seconds to handshake https. Could be a major issue if you're doing requests inside user sessions to build pages. mod_ssl can cache the handshakes, but only up to a point.
10 |600 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

eldk64 avatar image
0 Likes"
eldk64 answered
Hello @helios825, I was using https urls for Finding Api calls until this summer or at least september. Calls to https were redirected to http, so I fall back to http calls. Now it seems you have found that it is implemented ? Thanks, Eric
10 |600 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

eldk64 avatar image
0 Likes"
eldk64 answered
>I was using https urls for Finding Api calls until this summer or at least september. Sorry, it was shopping api. It's ok with Finding API.
10 |600 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

helios825 avatar image
0 Likes"
helios825 answered
@eldk64: I haven't yet tested https with Finding API. But I just learned of it, such as in the docs pages. Thanks for the info on the Shopping API. I guess it's lagging the Finding API for SSL support. @clickimusprime: Thanks for the tip. Hmmm, that may be a dealbreaker, unless the non-SSL endpoints are finally disabled and I'm forced to use https.
10 |600 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

eldk64 avatar image
0 Likes"
eldk64 answered
Hello, @helios I have done tests and posted here a comment with them for shopping API but it is under moderation and not yet published. https is not yet implemented for shopping API. https is ok for Finding API (TLS 1.2) but http2 is not (yet?) implemented.
10 |600 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.