Who we are
         •  We work in EPA’s IT Shop, the 
            Office of Environmental Information.
         •  Provide IT consulting 
            (recommendations and insight) to 
            EPA IT Development teams.
         •  Host EPA’s Developers’ Guild, a 
            monthly webinar available to EPA, 
            State and Tribe Partner Developers, 
            IT Professionals, and Project 
            Managers.
                                                                                       2
                                      U.S. Environmental Protection Agency
                 What we are going to share today
         •  Why REST APIs were used
         •  What was developed: REST API proof of concept
         •  What issues we ran into
         •  Suggestions for reuse
         •  Looking Ahead
         •  Contact
                                                                                     3
                                     U.S. Environmental Protection Agency
                      Why REST APIs were used
        •   Flexibility
             – REST API can handle multiple data calls.
             – Return data in different formats.
        •   Developers are familiar with REST APIs.
        •   Most modern languages have tooling to support REST APIs.
        •   Conclusion: Satisfy the need for Primacy Agencies to easily 
            submit data to the EPA.
                                                                                     4
                                     U.S. Environmental Protection Agency
           What was developed: API Proof of Concept
     •   The user interface was developed to: 
          – Make various GET request to an endpoint to make it easy to look up 
             identifiers such as Water System ID, Facility ID, Sample Point ID, and Lab 
             ID.
          – Make a POST request to send data of a Negative Coliform Test Sample.
     •   Demo Assumptions
          – PHP and Bootstrap were used to develop the API and UI.
          – Mock basic authentication.
          – Not all Primacy Agencies have Sampling Point ID or Lab IDs.
     •   Estimated time to develop the UI: 1 Developer part-time, 3-4 weeks
                                                                                      5
                                      U.S. Environmental Protection Agency
         DEMO: API PROOF OF CONCEPT
         - FAILED SUBMISSION 
         - TOTAL COLIFORM NEGATIVE SAMPLE 
         SUBMISSION
         - SEEING SUBMISSION IN SDWIS 
         DATABASE
                                                                                     6
                                     U.S. Environmental Protection Agency