The Web’s Largest API Search Directory

APIs are the lifeblood of mashups. I speculated here 5 years ago that manually assembled API directories (ProgrammableWeb being the apex of examples) were probably going to be supplanted by automated directories at some point. Then I waited… and waited…

It wasn’t happening; no one seemed to see the potential here. So recently, I decided to get down to business and try and solve the problem myself. The result is APIHound, the web’s largest API directory.

Over 50,000 APIs are in the searchable directory (or you can browse by category). It’s still a work in progress as you can read here. Among other features, I’d like to add the ability to bookmark/favorite cool APIs you discover and include a “featured API” widget on the homepage.

I think the site’s off to a great start though, so check it out!

Should you consider outsourcing management of public APIs?

Hey, getting back to mashup-related stuff (again, posting over at SearchSOA)

HTML5 or Native Apps? Which is Best?

Another guest post over at SearchSOA

Innovation competitions: Do they actually spur software innovation?

Check out my guest post over at SearchSOA

When Do I Get to Build My Own Portal?

My latest post over at SearchSOA, When Do I Get to Build My Own Portal, , describes an interesting mashup use case. We don’t often think of portals as mashups, because there is this notion that a mashup communicates information via a single point.

For example, in the classic “Show me nearby apartments on a map” mashup, the two underlying components may be craiglist and Google Maps. But you only see 1 output: A map with data points on it. A portal typically has a bunch of “little boxes” (portlets) that can be populated from a variety of different places, and they don’t necessarily interact with one another. So is it even proper to call a portal a mashup?

I think so. Although there might not be integration at the data level, the fact is the various portlets are mashed together at the presentation level. A portal provides a unified container to view disparate systems, even if the views inside that container aren’t necessarily mashed together. And the fact is that many “portal-enabling” tools that help you get content into a portal are in fact mashup products.

If you’ve read any of my previous posts, you know I am a big fan of users being able to create their own mashups inside corporate environments. I think that “self-serve IT” is the only way users will get many of the solutions they need since IT departments can’t afford to dedicate resource to every project out there. In my SearchSOA piece though, I might seem to contradict myself, since I don’t think users should build their own Portals.

My experience is that users who want a portal are really voicing a concern about information availability. If you just give them a portal framework, they will still have the same problem. You should attack the underlying issue first and expose more of the information your users want. If they then choose to build a portal with that data, so be it. But they might also build other tools (information dashboards, monitors, etc) that are actually what they really need. You don’t solve a problem by throwing a tool or a framework at it.

  • Blackbaud SKY
    The Blackbaud SKY API provides customers and partners access to open, industry-standard REST APIs allowing them to customize, integrate or extend functionality of Blackbaud solutions for fundraising and relationship management, digital marketing, advocacy, accounting, payments, analytics, school management, grant management, corporate social responsibility, and volunteerism. Blackbaud has been serving the social good industry for more […]
  • Polysync Transform
    The Polysync Transform REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method provides an interface to perform linear transformations on coordinate frames. Polysync provides a platform and features that allow for creating, testing, and deploying applications for driverless vehicles. Date […]
  • Polysync Socket
    The Polysync Socket REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method provides a wrapper around a network socket. Polysync provides a platform and features that allow for creating, testing, and deploying applications for driverless vehicles. Date Updated: 2017-01-09 Tags: […]
  • Polysync Serial
    The Polysync Serial REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method is wrapping around a serial port. Polysync provides a platform and features that allow for creating, testing, and deploying applications for driverless vehicles. Date Updated: 2017-01-09 Tags: [field_primary_category], […]
  • Polysync Shared Memory
    The Polysync Shared Memory REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method is providing an interface for reading and writing data from a shared memory queue. Polysync provides a platform and features that allow for creating, testing, and deploying […]
  • Polysync System Design File
    The Polysync system Design File REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method allows developers to interact with the system design file. Polysync provides a platform and features that allow for creating, testing, and deploying applications for driverless vehicles. […]
  • Polysync Record and Replay
    The Polysync Record & Replay REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method enables the coordination between nodes participating in log sessions. Polysync provides a platform and features that allow for creating, testing, and deploying applications for driverless vehicles. […]
  • Polysync Node
    The Polysync Node REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method is creating a Polysync Node. Polysync provides a platform and features that allow for creating, testing, and deploying applications for driverless vehicles. Date Updated: 2017-01-09 Tags: [field_primary_category], [field_secondary_categories]
  • Polysync Messaging
    The Polysync Messaging REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method is passing information using predefined messages. Polysync provides a platform and features that allow for creating, testing, and deploying applications for driverless vehicles. Date Updated: 2017-01-09 Tags: [field_primary_category], […]
  • Polysync Video
    The Polysync Video REST API allows developers to access and integrate the functionality of Polysync with other applications and to create new applications. The main API method provides an interface for images, video, and decoder devices. Polysync provides a platform and features that allow for creating, testing, and deploying applications for driverless vehicles. Date Updated: […]