Integrate api.data.gov for API keys and analytics

[gbinal]

Per the GSA API Standards, it's encouraged to integrate api.data.gov for API keys and analytics. It's open source, functional, already set up for cross-GSA use, and easy to implement.

We've made some initial progress adopting this at GSA, but it would be good to go all the way! That way, GSA can put forward a more consistent developer experience and GSA API teams will have robust API analytics and be able to stay in touch with the developers who use their APIs. Tracking implementation here:

• [x] analytics.usa.gov
• [x] Api.Data.Gov Admin API
• [x] Auctions API
• [x] Code.gov (issue)
• [X] Corporate Consumer Contact Information (deprecated)
• [ ] Data.gov CKAN API (issue)
• [ ] Data.gov Inventory.Data.gov API (issue)
• [X] DigitalGov Search API (deprecated)
• [x] Digital Signature Solution API
• [ ] eMuseum API
• [ ] FedBizOpps Documentation
• [X] Federal Agency Directory API Documentation (deprecated)
• [X] Federal Procurement Data System - FAADS API (deprecated)
• [x] Federal Procurement Data System - FPDS API (SOAP API)
• [ ] GEAR API ([issue]())
• [ ] Go.USA.gov API
• [X] Government Jobs API (scheduled to be deprecated)
• [X] Non-Gov URLs API (deprecated)
• [ ] Per Diem API
• [x] Sustainable Facilities Tool API
• [x] System for Award Management API
• [x] US Digital Registry API

[Ryandaydev]

@gbinal The following can be removed from the list above because they are deprecated:

• Corporate Consumer Contact Information
• DigitalGov Search API (replaced by multiple APIs)
• Non-Gov URLs API
• Federal Agency Directory API
• Federal Procurement Data System - FAADS API

Other notes:

• Government Jobs API will be deprecated in the future, so probably not making any enhancements.
• FedBizOpps Documentation points to a SOAP web service