What is Apigee?

Apigee is a Google API management platform which helps in exchanging data between legacy software, cloud applications and backend services. These days, many services and sites available to users are delivered through RESTful APIs. An API gateway acts as a medium to connect these sites and services with data, feeds, and proper communication capabilities.

Apigee Edge (GUI) is the tool we use to create policies, configurations, and custom code to front services with the addition of a proxy layer. This abstraction from backend services and applications allows us to have power over security, data formats, quota, analytics, and more. We develop and manage APIs for use between internal systems, as well as integrations with external partners.

Common Terms

Application Programming Interface (API) - a set of definitions and protocols for building and integrating application software.

API Proxy – We expose APIs on Apigee by implementing API proxies. API proxies decouple the API from your backend services, shielding those frontend services or applications from backend code changes. As you make backend changes to your services, apps continue to call the same API without any interruption.

API Product – API products are the central mechanism for authorization and access control to your APIs. In Apigee, API keys are provisioned, not for APIs themselves, but for API products. In other words, API keys are provisioned for bundles of resources with an attached service plan.

Developer App – Applications (aka Apps) are registered with an organization to obtain credentials that enable access to one or more API products.

Organizations – In Apigee Edge, our environments are segmented between two different organizations (aka org).  Our NON-PROD org is comprised of our lower environments like DEV and TEST.  While our PROD org contains UAT and PROD environments. Developer apps and credentials are not shared between these two organizations.  We also have Developer Portals that are specific to each org.

How can a team request work?

For the API team to take on new work, we require the following items:

1. Swagger – API documentation

   1. We prefer a Swagger but will also accept OpenAPI Spec v3.

   2. If the backend service is SOAP based, we will accept a WSDL.

   3. Both JSON and YAML formats are acceptable.

2. Postman Collection – A group of saved requests which contain valid payloads or parameters to get a success call.

3. Visio/Lucidchart/Workflow Diagrams - Paint the picture of where Apigee will fit in with the services.

4. Completed API Questionnaire - see attached document below:
   
   

Open

Once you have the above 4 items, please send an email to api.team@ferguson.com with the new work request and the required attachments. 

Who makes up the Apigee Team?

Product Owner/Manager – Austin Block
Architect – Jeff Lanier
Business Analyst – Jaimee Driscoll
Apigee Developers – Sarah Newport, Lisa Bradshaw, Matt Orlando

How do I get access to all the cool APIs?

For our Non-Prod Developer Portal – you will need to sign in with your Ferguson AD account. Only internal users have access to Apigee DEV and TEST environments.

For our Prod Developer Portal – you can sign in with your Ferguson AD account, Google account, or a Github account. Both internal and external users are able to request access to APIs in our Apigee UAT and PROD environments.

If you have any questions around utilizing our Developer Portals or getting appropriate access – please reach out to the API team at api.team@ferguson.com or fill out a Contact Us form.