eBayApi | Laravel eBay API wrapper around DTS\eBay API | REST library

I'd recently a problem with Rails cache during migration from Rails 3.2 to Rails 4. App was unable to read AR models from the cache (same time simpler objects like hashes, array worked well). But ruby was the same.

So please pay attention that some issues might happen, so better for you to try.

I suggest marshaled object to save in file with one version of ruby and read with another.

Did You tried to test token by the ebay developer testing tool? There is a tool where You can test tokens, headers, requests etc.

PS. Make sure that You choose right enviroment - sandbox or production. Token for the sandbox is different as token for production environment.

Seems to me that you are trying to deploy a server application to netlify which only supports client apps. You could make use of their functions offering if you want backend functionality tied with your client app.

After an additional day of research, trial, and uncountable errors I seem to have come across a way to deal with this issue.

The key is that the response object has many properties but none of them get filled in any way. It may be because these were used in some earlier implementation of the objects but are no longer used. You can see that nothing is filled except the "Any" property, which is the key.

The "Any" property receives an XmlElement object which contains the full response in XmlFormat. All I did was parse the Xml into an XDocument, then use LINQ to find and read the elements I was looking for, In the case of Getsuggestedcategories, I found the CategoryID elements and output the values to a list.

Here is a snippit of my code changes starting with the instanciating of the response object.

Alright, I managed to figure it out. The way to get it working is a bit of a doozy, there's probably a better way but I couldn't figure one out. Strap in.

Before I start, Microsoft has great docs about WCF here. Check them out if you're not familiar with WCF like me. This is using a client, not a server. We're just talking to eBay's server, not running our own.

Before the next step, make sure your solution builds. You cannot add a connected service unless it successfully builds.

First step is to add the service reference to the project and generate the model from eBay's server. eBay provides WSDL files for this purpose. We specifically want this one. You can use the Add Connected Service tool in Visual Studio to do this. You must have an ASP.NET project selected, then go to Tools > Add Connected Service. Use the option for Microsoft WCF Web Service Reference Provider. Enter that .wsdl URL in the URI box, click Go, change the namespace to whatever you want, then click Finish. The namespace is purely preference, I made mine EbayService. All other settings can be left as their defaults. A box will pop up with a bunch of logging stuff, you can ignore it and wait until it's finished. There will be a TON of yellow warnings, those can be ignored as well.

(Note: You can also use svcutility to generate the model instead of Visual Studio's GUI, but I won't cover that.)

The web project should now have a section in Solution Explorer near the top called Connected Services. There should be a folder within that's named whatever namespace you provided previously. Inside will be a file called Reference.cs that contains all of the parsing information for the eBay service. This file is MASSIVE, mine has nearly 122k lines. We need to do a couple of things in here.

We need to do a couple find/replace operations. To do this, we have to find/replace two strings. Turn on regex in the replace window, then replace , Order=\d{1,3} with nothing. This catches the cases where Order is one of multiple parameters on the attribute. Then do the same thing, but replace Order=\d{1,3}. Doing this breaks one of the classes that I came across, so find the class ReviseInventoryStatusRequestType. It has a field called any1Field and a property called Any1. Delete both of those.

Keep in mind you'll need to redo these steps if you ever regenerate the service from the server, as that process overwrites Reference.cs.

(Why do this? The eBay WSDL file specifies the order that elements will be in when they're returned from the API, but they're not even close to correct. Because of this, almost none of the responses will actually parse properly. We need to remove the order specifications and let the program handle the parsing via name.)

It's possible to work directly with this service, but doing so gets really messy. I therefore wrote a wrapper around the client that simplifies this greatly. Commented code is below, the DI will come in the next step so don't worry about that. You would need to add a function for each API endpoint that you'll use.

This property is an object containing properties mapped to the named route “parameters”. For example, if you have the route /user/:name, then the “name” property is available as req.params.name.

see: http://expressjs.com/en/4x/api.html#req.params

your route doesn't have any named parameters