2. What is an API. Application Programming Interface. That's jargon. It means nothing. Greg Elin called it a remote control for software. That's one way of thinking about it.
If you have a smartphone, it has a list of contacts, for any other program to access your contacts, it has to use the contacts' API. The contacts' API is essentially the set of instructions that define what can be done with your contacts and how to do it. In recent years, we learned that the APIs that governed access to contacts on some phones were too generous, so the APIs to access the contacts were changed.
4. So, I'm going to talk about GSA's Social Media Registry and its API. Particularly, I'm going to talk about the API-first approach that GSA took when building it. 5. The issue was this: we needed lists of what was official. People were getting spoofed. Agencies were afraid of being spoofed, or being unable to assert their authority. Previously, the .gov and .mil domains gave government their own *domain*, but as governments interact with citizens on .com domains – Twitter, Facebook, or Google+ – there's a need to know what's going on out there. Both by management within government, but by journalists and citizens.
6. But! How to build it? The old USA.gov way wouldn't work. *Fedsourcing*.7. And how to present it? We didn't know. So we went API first. We build an API to put stuff into the registry and an API to get stuff out. It's all documented at registry.usa.gov.