Introducing openFDA
Welcome to the new home of openFDA! We are incredibly excited to see so much interest in our work and hope that this site can be a valuable resource to those wishing to use public FDA data in both the public and private
Application programming interface
News and Events on Application programming interface
194 posts
New Go.USA.gov Features: Search Your URLs, Add Notes, New Bookmarklet, and More
You can now log in to Go.USA.gov with your username or email address, one of the new improvements added to the government URL shortener.
Welcome to the Future of Census.gov
If you have ever visited census.gov, you know that sorting through the vast array of information about America’s people, places and economy can be daunting. Based on customer research and feedback we collected and analyzed over time, we heard loud and clear
Alternative Fueling Station Locator App from the Department of Energy
So: You decided to purchase a car that takes advantage of more environmentally friendly fuel. Congratulations! Now, you need to find a place to fill the tank that offers more than just regular gas. The new Alternative Fueling Station Locator app from the folks at the Department of Energy’s National Renewable Energy Laboratory is a must-try. The new iPhone app will
U.S. Census Bureau Dwellr App
The pursuit of happiness for many of us might mean a fresh new start and a new place to call home. But where? In such a large and diverse country as ours, the choices can seem endless — and overwhelming. Now, your data friendly U.S. Census Bureau has harnessed the power
Content Management Systems Toolkit
Improving the federal government’s ability to deliver digital information anytime, anywhere, on any device via open content is a key goal of the Digital Government Strategy. A content management system (CMS) can help your agency move to an open content model, making it easier for people to find, share, use, and re-use your information.
Trends on Tuesday: The State of Mobile Search
Mobile searching has become a fact of life. According to a recent study by Econsultancy, 67% of smartphone owners had used their device to search for information in the past 7 days. The infographic below describes what they are searching for–the majority of searches are for
API Security
Like website development, API security revolves around three stages—planning the API, testing the API, and monitoring the API after it has launched. The planning stage requires those involved to conceptually map several design decisions and the impact that they will have on security. The second stage applies your agency’s security program to the API release
Chief Digital Officer: Roles and Responsibilities
In my previous blog post, I asked if your agency needs a Chief Digital Officer and before you answer maybe you’d want to know what exactly would a Chief Digital Officer (CDO) do at your Agency? According to Tim Bourgeois of ChiefDigitalOfficer.net , the biggest asset a CDO brings
Does Your Agency Need A Chief Digital Officer?
Russell Reynolds Associates, the senior-level executive search firm, says that the last 2 years have seen the rise of the Chief Digital Officer (CDO), a senior executive who sits at the right hand of the CEO. According to the consulting firm Gartner, 25% of organizations will have a Chief
Make Mobile Gov with the Mobile Application Development Program
Anytime, Anywhere, Any Device. The 21st century imperative to deliver government information and services to the public anytime, anywhere and on any device makes mobile a critical tactic in the federal Digital Government Strategy.
/Developer Kit
These are the elements that make up a well-rounded developer hub. Homepage The API efforts of any agency should all be accessible via one easy to reach developers hub. This Web page should provide a path to all public APIs and any associated resources. Once an agency has begun to publish multiple APIs, certain resources
API Release Kit
These are the elements you should include in your federal API release. Homepage Each of your public APIs needs a page to serve as a hub to provide access to all information and tools associated with it. By using the page’s sidebar, footer, and sub pages, you can directly include or link to each of
We the People API
“APIs for WhiteHouse.gov? What in the heck does that mean?” Like President Obama, you may be asking the same question.
New Healthcare.gov is Open, CMS-Free
Recently HHS CTO Bryan Sivak outlined a new vision for healthcare.gov. The site will relaunch this June with a completely rethought design and architecture. The new healthcare.gov follows a new CMS-free philosophy. It will be a completely static website, generated by Jekyll. This shift will allow HHS to move away from
APIs in Government
This page is about what an Application Programming Interface or API is and what it does and how government agencies are using them to operate more efficiently.
Producing APIs through Data.gov
One way agencies can offer APIs for their data is to use the built–in functionality of Data.gov. The information that is hosted as interactive datasets have an API layer which agencies can make available through documentation in the developer’s section of the agency’s website. The guide below will help you do this. Process Upload a dataset
Usability Testing + Gov APIs = Best
Good APIs can transform intimidating data sets into something that people can use. Good government APIs can create a better connection between government and citizens. The Digital Government Strategy has spurred Federal adoption of APIs, and the Digital Services Innovation Center and DATA.GOV teams are supporting these efforts by releasing a swath of guidance and
API Analytics
Similar to website analytics, API analytics focus on reliably reporting the metrics which are most useful to its stakeholders. There are a many ways of collecting, reporting, and consuming API analytics but all revolve around the industry–accepted norm that some form of analytics are crucial to any API program. The most basic metrics will track
API Design and Documentation
Design At their core, developers want APIs for very straightforward, pragmatic ends. You should always design your APIs and document them with the goal of making it easier for developers to use them. Doing so results in greater adoption and a healthier, more successful API. The least efficient way to support developers would be to
