We will make this library open source at some point in the near future. For now you are free to use the library & if you really want the code, shoot me an email!

//Create the OodleRequest object that will be serialized to the server
OodleRequest oodleRequest = new OodleRequest("TEST");
oodleRequest.Filter.location.Region = Regions.RegionTypes._usa;
oodleRequest.Paging.Start = 1;
oodleRequest.Paging.Num = 50;
oodleRequest.Filter.refinements = Filter.refinementsTypes.none;
oodleRequest.Paging.Sort = Paging.SortKey.ctime;
oodleRequest.Filter.attributes.AddPriceRange(5000, 6000);
oodleRequest.category = "vehicle";
oodleRequest.q = "honda civic";

//Creating the webrequest object - Notice that the oodleRequest is simply a string representation of your query which you can print to the screen for troubleshooting
WebRequest webRequest = WebRequest.Create(oodleRequest.ToString());
using (WebResponse response = webRequest.GetResponse())
{
    using (StreamReader reader = new StreamReader(response.GetResponseStream()))
    {
        //this will get the JSON result back from oodle
        string output = reader.ReadToEnd();
        //We do a minor alteration in the json string due to a problem oodle is facing with php's representation of objects as arrays
        output = output.Replace("\"location\":[]", "\"location\":{}").Replace("\"user\":[]", "\"user\":{}");
        OodleResult Result = JsonConvert.DeserializeObject<OodleResult>(output);
        //Now you can whatever you want with the results, you can start by iterating through Result.Listings to view all the listings your query returned
    }
}

You will notice that both the OodleRequest & OodleResponse objects represents a very similar structure to the structure defined by oodle in Oodle Api parameters

The Oodle Response is broken down to 5 main parts

• Current – This contains information about the query that is returned, (ex. Region, Category, Start item #, Num or items returned).
• Listings – This is a strong typed array of Listings. The maximum you will ever find is 50 items as defined by oodle
• Meta – Metadata details on the results available. How many total items available for your search query…etc. This is very important if you are implementing paging in your result set.
• Refinements – by default this is null unless you have requested refinements in your oodle request (ex. oodleRequest.Filter.refinements=none | simple | full)
• Stat – should always be “ok” if everything runs good.

Everything else is really self explanatory and you can depend on your IDE’s intellisense to guide you. Feel free to comment on this post if you have any Qs.

Let me know your feedback!! :)

We’ve also added a section in our FAQs that can help answer questions you might have about how it works.

If you have anything listed on eBay you owe it to yourself to check this out. It’s free, it will bring more visibility to your item(s), and it takes less than a few minutes to import hundreds of your pre-existing listings with a few clicks.

Click here to check it out!

I really enjoy receiving feedback from my visitors so please if you have something to say (good or bad) don’t hesitate to contact us or comment on this post.

Thanks!
-Ash

Viewing photos of all comparable items you are intersted in is worth a lot when you are searching for anything. The last thing you need is somebody explaining every single detail about every item before you’ve even seen it.

This is why I’ve been busy the past few days to bring a more visual aspect to ad browsing in Love2Trade.

Photo View will allow you to take a quick glance on all items with photos before you even bother with the details that might not be necessary until you like what you see.

Below are sample search results for Ford F-150 in the Houston area.
.

Now love2trade visitors search queries will include results from both love2trade listings as well as oodle, this will give our visitors access to millions of listings in the US, Canada & the UK.

-Ash