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.

  • Twilio Lookups
    The Lookups API offers information about a phone number such as region-specific formatting, carrier details, and caller name information. Each request can obtain 1 or more types of data. This API returns information in JSON format, and requires API Keys for authentication. Twilio is a San Francisco based telephony infrastructure provider. Date Updated: 2016-08-24 Tags: […]
  • Dimelo
    Dimelo is a French customer engagement firm that provides social customer service technologies. Dimelo unifies social media messages, forum and communities, chat, and mobile messages in one system. The Dimelo API uses webhooks to deliver a digital platform that can be integrated with Facebook pages, processes, applications, and websites. Developers need to contact Dimelo directly […]
  • Outlook Notifications REST
    This REST API allows apps to learn about changes to the user's mail, calendar, or contact data secured by Azure Active Directory in Office 365. Data includes;,,,, and Date Updated: 2016-08-23 Tags: [field_primary_category], [field_secondary_categories]
  • Outlook People REST
    This REST API gains access to data secured by Azure Active Directory in Office 365. It allows you to get information about the people from across mail, contacts, and social networks. This includes access to Microsoft accounts in:,, and Date Updated: 2016-08-23 Tags: [field_primary_category], [field_secondary_categories]
  • Office 365 Data Extensions REST
    This REST API allows apps to store custom data in a message, event, or contact of the user's account. The account can be on Office 365 or Microsoft and includes;,,, and Date Updated: 2016-08-23 Tags: [field_primary_category], [field_secondary_categories]
  • Microsoft Azure Active Directory Graph REST
    This API provides programmatic access to Azure Active Directory and allows apps to perform; create, read, update, and delete (CRUD) operations on directory data and directory objects. This includes; users, groups, and organizational contacts. Azure Active Directory (Azure AD) is Microsoft’s multi-tenant cloud based directory and identity management service. Date Updated: 2016-08-23 Tags: [field_primary_category], [field_secondary_categories]
  • NASA EONET Categories
    This EONET REST API can be used to filter the output of the Categories API and the Layers API. Categories are the types of events by which individual events are cataloged. EONET is The Earth Observatory Natural Event Tracker, a prototype web service with the goal of: providing a curated source of continuously updated natural […]
  • Aquaplot
    Aquaplot offers sea routing functionality and distance computation for ships. Developers can build integrations related to route planning, route optimization, fleet maneuver planning, and traffic monitoring. The Aquaplot API allows developers to retrieve the distance between 2 coordinates in water. The database contains 3,500 ports. This API uses JSON for responses, and GeoJSON will be […]
  • NASA Vesta Trek REST
    This API is a part of a collection of APIs that power the Vesta Trek NASA web-based portals for exploration. Map layers are available through OGC RESTful WMTS protocol. NASA open data supports NASA’s scientists and engineers with information technology such as infusion, procurement, and future IT workforce development. Date Updated: 2016-08-22 Tags: [field_primary_category], [field_secondary_categories]
  • NASA TechPort OpenData Support REST
    This REST API can be used to export NASA's TechPort data into an XML format to be further processed and analyzed as technology project data to be available as machine-readable. NASA open data supports NASA's scientists and engineers with information technology such as infusion, procurement, and future IT workforce development. Date Updated: 2016-08-22 Tags: [field_primary_category], […]