Posted on 10-22-2011
Last spring when I started writing for ProgrammableWeb, my first post was "Everything Should Be an API," Says FCC. The story was about the new FCC web site, that was built entirely on top of RESTful APIs using the Drupal platform.
Since that post, I met the company behind the FCC website redesign, Seabourne Inc., which builds some pretty innovative solutions using Drupal, employing APIs in everything they do. As part of the FCC.gov website project, Seabourne Inc. built a module for Drupal that leverages the platform for content publishing, powered by APIs.
I spoke with Mike Reich, the CEO of Seabourne Inc. about APIs, he is as passionate about APIs as I am, but has identified the best place to start when it comes to opening up the government, is with content APIs instead of just focusing on data APIs.
He’s right. In the rush to open up government data, many of us overlook the huge archives and content generated on a daily basis by our government. Recently, many government agencies are adopting Drupal as a content management platform, and using Seaborne’s Content API for Drupal, any agency or organization can make content openly accessible via an API.
Their Content APIs can instantly make content from an agencies website available for other agencies to access in a self-service way, reducing the resources needed for inter-departmental coordination. In addition to making external coordination more efficient, it can make rolling out separate web sites, applications and mobile apps much more cost efficient as well.
Content APIs can also open content to the public allowing media, companies and even individuals to pull content and mash it up, evolve, derive meaning and stories from it that a government agency may not have time or even perspective to do. In my opinion this type of content access by the public truly reflects the next generation of democracy, allowing anyone to get involved in government, even demonstrating better ways to understand how government operates.
You can access the Content API for Drupal on the Seaborne Inc. website, I’m installing a prototype Drupal website so I can play with the API, helping me understand whats possible when using Drupal in conjunction with the Content API.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Providing Users With Reciprocity Tools So Important Intuit Purchases itDuzzit
- Bing Developer Assistant for Visual Studio Delivers Relevant API Code
- Average Number of APIs Used In A Modern App
- An APIs.json Collection Of API Resources Across Your Public, Partner Or Internal Resources
- One Possible Reboot Of The API Stack
- How Are Dev Shops In Chicago Using APIs? A Talk With Bryson Pouw At Blaze Portfolio
- Every API Provider Should Have A Logo And Branding Page
- What Is An API First Strategy? IT architecture And Catalyst For Engagement
- The Speed Of Federal Government When It Runs On Github
- Swagger, APIs.json, And Review For The New Developer.Trade.gov
- Student, Instructor, Classroom, Class, And Course API Planning At BYU
- Can You Add My API To Your Website Listing?
- Adding Google To List Of API Deployment Companies
- What Is An API First Strategy? Adding Some Dimensions To This New Question
- The Five Month Journey Toward A Stable APIs.json Discovery Format
- How Are Mobile Dev Shops In Chicago Using APIs? A Talk With Dave Devitt At SYDCON
- An API Case Study Format From Google Cloud Platform
- Next Stable Version of APIs.json + APIs.io Is Ready - Are Your APIs Discoverable?
- Expanding API Gateway Connectors Into A World of API Deployment Startups
- Where The Good IPAs Are In Chicago While At API Strategy And Practice In September
- The Blog For Your API Is The Most Important Signals You Can Send
- Public APIs Are Tough When You Are In A Tightly Controlled Industry
- Give Me A URL To Request Then Store My API Keys In My Private Github Repo
- Mapping The World Of Internal APIs Via Rogue API Registry
- Continuing With The API Restaurant Analogy