Home

A Saner (and Geekier!) Approach to Working with APIs

What is this?

Software developers know that using APIs can be a nuisance, because you have to

• study the API documentation (often complex, or poorly written)
• find and evaluate available libraries for using the API
• write code that couples your application with the API -- or define an abstraction layer
• worry about the performance impact of making synchronous API calls -- or put in place a framework for background jobs
• decide how to handle errors

We make all of this easier. Geekier provides

• machine-readable API descriptions, created by experts and organized around how to use these APIs to get things done
• a simple abstraction layer to use in your code, avoiding vendor lock-in and providing lots of flexibility
• a service framework that actually makes API calls
• easily customized hooks for logging, retry policies, error reporting, and analytics

Can I see an example?

Example.

This reminds me of SPORE ...

Our API descriptions are based on SPORE.

How can I help?

If you believe that an interoperable web needs a open framework for connecting applications and services based on self-describing APIs, join us!

Extending the reach of Geekier benefits the entire community. You can do this by contributing new API descriptions, or libraries making Geekier accessible from other programming languages (so far we've got Ruby covered). Talk to us if you want a more specific suggestion.