This pageapplies toApigee andApigee hybrid.

A deployment is an API hub entity that describes where an API is hosted. It represents a specific runtime instance of an API, whether it's a traditional REST API, an agentic API using the Model Context Protocol (MCP), or any other style. For example, a deployment could represent an Apigee API proxy, an API deployed to Google Cloud API Gateway, or APIs deployed to other Google Cloud services or non-Google Cloud services.

You can associate an API version with multiple deployments to model scenarios such as dev, staging, user acceptance testing (UAT), and production deployments corresponding to a given version. You can also associate multiple versions with a single deployment in cases where multiple versions of an API (or potentially different APIs) are deployed together.

A deployment entity includes metadata such as name, display name, description, and associated versions. The following three attributes are required to create a deployment in API hub and specify details about the deployed API:

• Deployment type: Specifies the type of deployment, such as Apigee, Apigee hybrid, Apigee Edge Private Cloud, and others.
• Resource URI: A URI to the deployment resource. For example, if the deployment resource is an Apigee API proxy, then this field must specify the URI to the management user interface of the proxy.Note: ForApigee deployment types, we recommend that the Resource URI conforms to the following format:organizations/([^/]+)/environments/([^/]+)/apis/([^/]+)$

  For example, the Resource URI for an Apigee API proxy deployed to theprod environment of themyorg organization isorganizations/myorg/environments/prod/apis/iloveapis.

• Endpoints: The endpoints on which the actual deployment of the API is listening to requests. For example, this field could be a list of IP addresses or hostnames.

What's next

• Learn how tomanage deployments.
• Learn how tomanage versions.