Site Logo

Props to Oodle API Developers

Massive PropsHey everyone, Steve Baker here from the Engineering team at Oodle.

I wanted to take a brief moment here and give some props to my fellow nerds out there in the Oodle developer community who are doing some great things on top of the Oodle API.

We have several bigger partners who are making good use of the Oodle API, such as:

Redfin — Redfin recently came on board as an Oodle API partner, using Oodle data to flesh out their database of real estate listings. Their engineers have been especially helpful, pinging us with requests and suggestions for Oodle API enhancements during their development process.

Backpage — Backpage uses the Oodle API to provide extra listings at the end of Backpage search results. (Example here.) They’ve been a long-time partner and we’re happy to be a part of their solution.

Listpic — Ryan Sit did a great job in creating one of the most fun and visually interesting classifieds sites you’ll come across. Head to a Listpic search results page (example: Cars in San Francisco) and you’re presented with a series of thumbnails that can be sized up and down through the use of a slider bar at the top of the page. All of the classified listings at Listpic.com are from Oodle API. Solid.

I have a special place in my heart, though, for all the folks out there who are making it easy for fellow Oodle API developers to do neat stuff:

Joplin Crashpad — When talking about awesome Oodle API developers, I have to start here. Yahoo! user “CrashDaddy” is an all-star on our Oodle API group at Yahoo. He regularly jumps in and answers questions from fellow developers, even pitching in with full sample code in some cases. He runs a fun community site for Joplin, Missouri — called “Joplin Crashpad” — with listings powered by Oodle. It’s a fun place and we love him for his enthusiasm.

Ricardo Covo — One of the requests we receive most often on our API support email address is to provide .NET sample code and/or .NET client libraries for the Oodle API. Ricardo has done just that, writing a C# .NET wrapper for the API and publishing the source code for others to use. Awesome work.

WordPressIntoCMS.com — They recently rolled up their sleeves, revised some WordPress page templates, and inserted extra code to “dynamically [display Oodle ads] for each WordPress Post“. They used the PHP5 client library that we posted on developer.oodle.com to call the Oodle API when the WordPress page template is displayed. Doesn’t look like their code is in heavy use yet around that site, but I can’t wait to see it all in action.

There’s plenty of other great stuff going on in the Oodle API community. You can find other examples in the “Oodle API In Action” section on our Oodle Developer Center.

We’re working hard this spring and summer to make the Oodle API both easier and more powerful. I know that you’ll like what we’re cooking up. If you’re interested in checking out the Oodle API, head on over to the Oodle Developer Center. Thanks to everyone for doing such great work! Keep on hackin’.

3 Responses to “Props to Oodle API Developers”

  1. May 28th, 2008 at 2:47 pm

    Brian Bailey says:

    This is Brian from WordPressIntoCMS. Thanks very much for the praise, Steve. Your tips over at the Oodle discussion group have been quite helpful to me.

    Just to clarify, the system I devised is being used extensively and to great effect at Metro-East.com.

  2. May 28th, 2008 at 6:43 pm

    Ricardo Covo says:

    Hey Steve,

    Thanks for you reference to the .Net library, I hope many of the upcoming .Net developers will find it useful.

    Also, I wanted to comment that the link to my blog is broken; can you please fix it? (it as a double HTTP it seemst). Thanks a lot!

    -Ricardo

  3. June 26th, 2008 at 6:46 pm

    Crashdaddy says:

    Thanks, SteveB, for the good words! :blush:

Leave a Reply