viewing Apigee X documentation.
View Apigee Edge documentation.
This page explains some basic terminology related to Apigee.
|Google Cloud projects||
Google Cloud projects form the basis for creating, enabling, and using all Google Cloud services including managing APIs, enabling billing, adding and removing collaborators, and managing permissions for Google Cloud resources.
You need to create a Google Cloud project before you can create and provision an Apigee organization.
|Provisioning||Provisioning is the process for installing and configuring Apigee.|
An organization is a container for everything related to Apigee in your Google Cloud project, including API proxies, services, and the resources needed to support them. You create your organization during provisioning.
An Apigee environment is a runtime execution context—that is, an isolated software environment, within an organization, where you can create and deploy API proxies using Apigee. You can create multiple environments in an organization.
An environment group is a group of Apigee environments with a single hostname. The hostname can be used to call API proxies deployed to any environment in the environment group.
An API proxy is an interface between incoming requests and the backend services the API provides. The proxy uses policies to processes all incoming requests and outgoing responses from the backend.
Instances correspond to Google Cloud regions, and there can only be one Apigee instance per Cloud region.
A policy is a processing step that is executed by an API proxy. Apigee provides many pre-defined policies that perform various API tasks, such as transforming message formats or enforcing access control.
For additional terminology, see Glossary.