Select your organization from the dropdown menu in the upper left corner.
Select Proxy development > API proxies in the main view.
Click Create.The API Proxy Wizard starts.
Select Reverse proxy (most common).
The Proxy details view is displayed.
Configure your proxy with the following settings:
Proxy name: Enter myproxy. The remaining steps in this section assume
that this is your proxy's ID.
Base path: Automatically set to / followed by the
proxy name, which in this example is /myproxy. The Base
path is part of the URL used to make requests to your API. Apigee uses the URL to
match and route incoming requests to the proper API proxy.
(Optional) Description: Enter a description for your new API proxy, such
as "Testing Apigee hybrid with a simple proxy".
Target (Existing API): Enter "https://mocktarget.apigee.net". This defines the
target URL that Apigee invokes on a request to the API proxy. The mocktarget service is
hosted at Apigee and returns simple data. It requires no API key or access token.
Your API proxy's details should look like the following:
Click Next.
Under Deploy (optional), you have the option to select one or more
environments
in which to deploy your proxy, in the Deployment environments field.
If you prefer not to deploy the proxy at this
point, leave the Deployment environments field empty. You can always deploy
the proxy later.
Click Create.
Apigee generates the proxy (sometimes referred to as the proxy bundle).
Apigee displays the Proxy summary view.
If you chose to deploy the proxy, the Deployments section displays the Revision
number, which is 1 when you first deploy. The Status column displays the
environments in which the proxy is deployed with a green status indicator.
Below that, the Revisions section shows all revisions made to this proxy. By
clicking on one of the VIEW items in the Endpoint summary column, the
Endpoint section displays:
Proxy endpoints: The basepath you set for the proxy, which is this example
is /myproxy.
Target endpoints: The basepath you set for the target, which in this
example is https://mocktarget.apigee.net.
Select your organization from the dropdown menu in the upper left corner.
Select Develop > API Proxies in the main view.
Click Create New.The API Proxy Wizard starts.
Select Reverse proxy (most common).
The Proxy details view is displayed.
Configure your proxy with the following settings:
Proxy Name: Enter "myproxy". The remaining steps in this section assume
that this is your proxy's ID.
Proxy Base Path: Automatically set to "/myproxy". The Proxy Base
Path is part of the URL used to make requests to your API. Apigee uses the URL to
match and route incoming requests to the proper API proxy.
(Optional) Description: Enter a description for your new API proxy, such
as "Testing Apigee hybrid with a simple proxy".
Target (Existing API): Enter "https://mocktarget.apigee.net". This defines the
target URL that Apigee invokes on a request to the API proxy. The mocktarget service is
hosted at Apigee and returns simple data. It requires no API key or access token.
Your API proxy's details should look like the following:
Click Next.
On the Common policies screen, select Pass through (no authorization) as the
security option.
Click Next.
On the Summary screen, select an environment to deploy your proxy to and
click Create and Deploy.
Hybrid generates the proxy (sometimes referred to as the proxy bundle) and deploys it to the environment you selected.
Click Go to proxy list.
Apigee displays the Proxies view, which displays a list of API proxies. Your
new proxy should display with a green status indicator, meaning that it has been deployed.
2. Call the API proxy
When the UI indicates your proxy is deployed, you can try calling it using cURL or the REST
client of your choice.
For example:
Find the external IP address and port of the Apigee ingress gateway with the following command:
kubectl get svc -n APIGEE_NAMESPACE -l app=apigee-ingressgateway
Your output should look something like:
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
apigee-ingressgateway-prod-hybrid-37a39bd LoadBalancer 192.0.2.123 233.252.0.123 15021:32049/TCP,80:31624/TCP,443:30723/TCP 16h
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[],[],null,["Now that you've installed and configured the Apigee hybrid\nruntime and ingress gateway, you're ready to see how it all works together.\n\n1. Create a new API proxy using the Apigee UI\n\nThis section describes how to create a new API proxy in the UI using the API Proxy Wizard.\n**Note:** There is a new version of the Apigee UI, which is integrated with the Google Cloud console. The new UI is called *Apigee in Cloud console*. The instructions in the first two tabs below explain how to use either Apigee in Cloud console or classic Apigee UI. \n\nApigee in Cloud console\n\nTo create a new API proxy using Apigee in Cloud console:\n\n1. Open [Apigee UI in Cloud console](https://console.cloud.google.com/apigee) in a browser.\n2. Select your organization from the dropdown menu in the upper left corner.\n3. Select **Proxy development \\\u003e API proxies** in the main view.\n4. Click **Create**.The API Proxy Wizard starts.\n5. Select **Reverse proxy** (most common).\n\n The **Proxy details** view is displayed.\n6. Configure your proxy with the following settings:\n - **Proxy name:** Enter **myproxy**. The remaining steps in this section assume that this is your proxy's ID.\n - **Base path:** Automatically set to **/** followed by the proxy name, which in this example is **/myproxy** . The **Base\n path** is part of the URL used to make requests to your API. Apigee uses the URL to match and route incoming requests to the proper API proxy.\n - (Optional)**Description:** Enter a description for your new API proxy, such as \"Testing Apigee hybrid with a simple proxy\".\n - **Target (Existing API):** Enter \"https://mocktarget.apigee.net\". This defines the target URL that Apigee invokes on a request to the API proxy. The mocktarget service is hosted at Apigee and returns simple data. It requires no API key or access token.\n\n Your API proxy's details should look like the following:\n\n7. Click **Next**.\n8. Under **Deploy (optional)** , you have the option to select one or more environments in which to deploy your proxy, in the **Deployment environments** field. If you prefer not to deploy the proxy at this point, leave the **Deployment environments** field empty. You can always deploy the proxy later.\n9. Click **Create** . Apigee generates the proxy (sometimes referred to as *the proxy bundle* ).\n\n \u003cbr /\u003e\n\nApigee displays the **Proxy summary** view.\nIf you chose to deploy the proxy, the **Deployments** section displays the **Revision**\nnumber, which is 1 when you first deploy. The **Status** column displays the\nenvironments in which the proxy is deployed with a green status indicator.\n\nBelow that, the **Revisions** section shows all revisions made to this proxy. By\nclicking on one of the **VIEW** items in the **Endpoint summary** column, the\n**Endpoint** section displays:\n\n- **Proxy endpoints** : The basepath you set for the proxy, which is this example is `/myproxy`.\n- **Target endpoints** : The basepath you set for the target, which in this example is `https://mocktarget.apigee.net`.\n\nClassic Apigee\n\nTo create a new API proxy using Classic Apigee:\n\n1. Open [Apigee UI](https://apigee.google.com) in a browser.\n2. Select your organization from the dropdown menu in the upper left corner.\n3. Select **Develop \\\u003e API Proxies** in the main view.\n4. Click **Create New**.The API Proxy Wizard starts.\n5. Select **Reverse proxy** (most common).\n\n The **Proxy details** view is displayed.\n6. Configure your proxy with the following settings:\n - **Proxy Name:** Enter \"myproxy\". The remaining steps in this section assume that this is your proxy's ID.\n - **Proxy Base Path:** Automatically set to \"/myproxy\". The **Proxy Base\n Path** is part of the URL used to make requests to your API. Apigee uses the URL to match and route incoming requests to the proper API proxy.\n - (Optional)**Description:** Enter a description for your new API proxy, such as \"Testing Apigee hybrid with a simple proxy\".\n - **Target (Existing API):** Enter \"https://mocktarget.apigee.net\". This defines the target URL that Apigee invokes on a request to the API proxy. The mocktarget service is hosted at Apigee and returns simple data. It requires no API key or access token.\n\n Your API proxy's details should look like the following:\n\n7. Click **Next**.\n8. On the **Common policies** screen, select **Pass through (no authorization)** as the security option.\n9. Click **Next**.\n10. On the **Summary** screen, select an environment to deploy your proxy to and click **Create and Deploy** .\n\n Hybrid generates the proxy (sometimes referred to as *the proxy bundle*) and deploys it to the environment you selected.\n11. Click **Go to proxy list** .\n\n Apigee displays the **Proxies** view, which displays a list of API proxies. Your\n new proxy should display with a green status indicator, meaning that it has been deployed.\n\n2. Call the API proxy\n\nWhen the UI indicates your proxy is deployed, you can try calling it using cURL or the REST\nclient of your choice.\nFor example:\n\n1. Make sure your `DOMAIN` environment variable is set to the domain name you used for the hostname for your environment group in [Project and org\n setup - Step 3: Create an environment group](/apigee/docs/hybrid/v1.15/precog-add-environment). \n\n ```\n echo $DOMAIN\n ```\n2. Find the external IP address and port of the Apigee ingress gateway with the following command:\n\n ```\n kubectl get svc -n APIGEE_NAMESPACE -l app=apigee-ingressgateway\n ```\n\n\n Your output should look something like: \n\n ```\n NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE\n apigee-ingressgateway-prod-hybrid-37a39bd LoadBalancer 192.0.2.123 233.252.0.123 15021:32049/TCP,80:31624/TCP,443:30723/TCP 16h\n ```\n3. Export your external IP and port to variables: \n\n export INGRESS_IP_ADDRESS=EXTERNAL_IP_ADDRESS\n export INGRESS_PORT=\u003cvar translate=\"no\"\u003ePORT_NUMBER\u003c/var\u003e\n\n4. Call the API proxy: \n\n ```\n curl -H Host:$DOMAIN --resolve \\\n $DOMAIN:$INGRESS_PORT:$INGRESS_IP_ADDRESS \\\n https://$DOMAIN:$INGRESS_PORT/myproxy -k -v\n ```\n\n\n For example: \n\n ```\n curl -v -H Host:example.com --resolve example.com:443:233.252.0.123 https://example.com:443/myproxy -k -v\n ```\n5. A successful call to the proxy returns an HTTP 200 response code and the following output.\u003cbr /\u003e\n\n ```\n Hello, Guest!\n ```\n\n\nTo learn more about building and deploying API proxies, see [Build your first proxy overview](/apigee/docs/api-platform/get-started/get-started).\n| **Congratulations!**\n|\n| You've successfully installed Apigee hybrid. To learn more about building and deploying\n| API proxies, see [Introduction to API proxy building](/apigee/docs/api-platform/fundamentals/build-simple-api-proxy)."]]