Ahora que creaste un proxy nuevo, puedes probarlo mediante una llamada al proxy. Si se configuró una entrada del sistema de nombres de dominio (DNS) para el nombre de host del grupo de entornos de tu organización, puedes llamar al proxy de la siguiente manera:
curl https://YOUR_ENV_GROUP_HOSTNAME/myproxy
En el ejemplo anterior, YOUR_ENV_GROUP_HOSTNAME es el nombre de host para un grupo de entornos que contiene el entorno en el que se implementa el proxy. Consulta Encuentra el nombre de host del grupo de entornos.
Una llamada correcta al proxy muestra el siguiente resultado:
Hello, Guest!
Si el nombre de host del grupo de entornos se configuró durante el aprovisionamiento mediante un servicio comodín, como nip.io, puedes llamar al proxy sin tener configurada una entrada de DNS. Por ejemplo:
Si el host no se puede resolver, por ejemplo, recibes un error 404, vuelve a verificar que estés usando el nombre de host y el del proxy correctos. Puedes
encontrar el nombre de host en la IU de Apigee. Ve a Administrador > Entornos > Grupos para ver el nombre o los nombres de host.
Si ves un error de TLS/SSL, como un error de protocolo de enlace SSL, comunícate con tu proveedor de DNS para asegurarte
de que el registro A de DNS para el nombre de host esté configurado de forma correcta. Asegúrate de que el registro tenga la IP del balanceador de cargas que se creó durante el aprovisionamiento de Apigee.
Si no sabes cuál debería ser la IP, consulta
Determina si el balanceador de cargas de Cloud está configurado para un nombre de host.
Si ves un error de certificado TLS/SSL, es posible que el certificado SSL asociado con el balanceador de cargas no
tenga el nombre de host correcto y, por lo tanto, se rechaza. El certificado se creó durante el proceso de aprovisionamiento.
Los pasos para solucionar problemas en
Determina si el balanceador de cargas de Cloud está configurado para un nombre de host muestran cómo ubicar e inspeccionar el certificado.
Si no puedes resolver el problema, comunícate con la persona que aprovisionó Apigee para obtener más asistencia.
Busca el nombre de host del grupo de entornos
Si no conoces el nombre de host del grupo de entornos, puedes encontrarlo de la siguiente manera:
En la IU de Apigee, selecciona Administrador > Entornos > Grupos.
Busca una fila que muestre el entorno en el que se implementó el proxy. Por ejemplo, si el entorno es test-1, la fila puede aparecer como se muestra a continuación:
El nombre de host del grupo de entornos para este entorno es api-test.exco.com.
En este caso, el comando curl para llamar al proxy sería el siguiente:
curl https://api-test.exco.com/myproxy
En el siguiente paso, cambiarás el extremo de destino para que muestre datos XML del servicio de destino.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis page provides instructions for testing an API proxy in Apigee or Apigee hybrid, offering guidance for both the new Apigee in Cloud console and the classic Apigee UI.\u003c/p\u003e\n"],["\u003cp\u003eAccessing the API proxy involves finding the environment group hostname, which is determined by either an external or internal network configuration, requiring specific \u003ccode\u003ecurl\u003c/code\u003e commands for each.\u003c/p\u003e\n"],["\u003cp\u003eSuccessful API proxy calls will return the output "Hello, Guest!", otherwise potential issues may be due to timeout errors, incorrect hostnames, misconfiguration of the environment group hostname, or TLS/SSL certificate problems.\u003c/p\u003e\n"],["\u003cp\u003eSteps for the classic Apigee UI are to go to Admin > Environments > Groups, then View in Google Cloud Console to access the environment groups to find the proper hostname.\u003c/p\u003e\n"],["\u003cp\u003eA successful call will return "Hello, Guest!".\u003c/p\u003e\n"]]],[],null,["# Step 3: Call an API proxy\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nIn this step, you will test the API proxy you just created and deployed. \n\n### Apigee in Cloud console\n\n1. In the Google Cloud console, go to the **Apigee \\\u003e Management \\\u003e Environments** page.\n\n [Go to Environments](https://console.cloud.google.com//apigee/environments)\n2. Make sure the same Google Cloud project where you created the API proxy is selected from the dropdown at the top of the page.\n3. Select the **Environment Groups** tab.\n4. In the table, find the row for the environment group that contains the environment where **myproxy** is deployed. The hostname appears in the **Host Names** column of this row. For example: `mydomain.com`.\n5. Call the API proxy. The way you call the proxy depends on whether your Apigee instance is configured for external or internal network access. If you aren't sure how your Apigee instance is configured, contact your Apigee administrator.\n - **External access** : If your Apigee instance is configured for external access, call the proxy as follows: \n\n ```\n curl https://YOUR_ENV_GROUP_HOSTNAME/myproxy\n ```\n\n Where \u003cvar translate=\"no\"\u003eYOUR_ENV_GROUP_HOSTNAME\u003c/var\u003e is the hostname you obtained in the\n previous step.\n\n For example: \n\n ```\n curl https://mydomain.com/myproxy\n ```\n\n Here's another example, where the wildcard DNS service `nip.io` is used for the host: \n\n ```\n curl https://198.51.100.251.nip.io/myproxy\n ```\n - **Internal access** : If your Apigee instance is configured for internal network access, some extra steps are needed to obtain access to the internal load balancer and its IP address. For details, see [Calling a proxy with internal-only access](/apigee/docs/api-platform/get-started/accessing-internal-proxies).\n6. A successful call to the proxy returns the following output:\u003cbr /\u003e\n\n ```\n Hello, Guest!\n ```\n\n### Classic Apigee UI\n\n1. Open the [Apigee UI](https://apigee.google.com) in a browser.\n2. Make sure the same Google Cloud project where you created the API proxy is selected from the dropdown at the top of the page.\n3. In the Cloud console UI, select **Admin \\\u003e Environments \\\u003e Groups**.\n4. Click **View in Google Cloud console**.\n5. Select the **Environment Groups** tab.\n6. In the table, find the row for the environment group that contains the environment where **myproxy** is deployed. The hostname appears in the **Host Names** column of this row. For example: `mydomain.com`.\n7. Call the API proxy. The way you call the proxy depends on whether your Apigee instance is configured for external or internal network access. If you aren't sure how your Apigee instance is configured, contact your Apigee administrator.\n - **External access** : If your Apigee instance is configured for external access, call the proxy as follows: \n\n ```\n curl https://YOUR_ENV_GROUP_HOSTNAME/myproxy\n ```\n\n Where \u003cvar translate=\"no\"\u003eYOUR_ENV_GROUP_HOSTNAME\u003c/var\u003e is the hostname you obtained in the\n previous step.\n\n For example: \n\n ```\n curl https://mydomain.com/myproxy\n ```\n\n Here's another example, where the wildcard DNS service `nip.io` is used for the host: \n\n ```\n curl https://198.51.100.251.nip.io/myproxy\n ```\n - **Internal access** : If your Apigee instance is configured for internal network access, some extra steps are needed to obtain access to the internal load balancer and its IP address. For details, see [Calling a proxy with internal-only access](/apigee/docs/api-platform/get-started/accessing-internal-proxies).\n8. A successful call to the proxy returns the following output:\u003cbr /\u003e\n\n ```\n Hello, Guest!\n ```\n\nIf you get an error, check the following:\n\n- If you see a timeout error (unusual), try [undeploying and\n redeploying](/apigee/docs/api-platform/deploy/ui-deploy-new) the new API proxy.\n- If the host cannot be resolved, for example you receive a 404 error, double check that you are using the correct hostname and proxy name.\n- Make sure the environment group hostname is configured with the Cloud Load Balancer. See [Determining whether the Cloud Load Balancer is configured for a hostname](/apigee/docs/api-platform/fundamentals/environmentgroups-working-with#determining-whether-the-cloud-load-balancer-is-configured-for-a-hostname).\n- If you see a TLS/SSL error, such as an SSL handshake error, contact your DNS provider to make sure the DNS A record for the hostname is configured properly. Make sure the record has the IP of the load balancer that was created during Apigee provisioning. If you're not sure what the IP should be, see [Determining whether the Cloud Load Balancer is configured for a hostname](/apigee/docs/api-platform/fundamentals/environmentgroups-working-with#determining-whether-the-cloud-load-balancer-is-configured-for-a-hostname).\n- If you see a TLS/SSL certificate error, the SSL certificate associated with the load balancer might not have the correct hostname, and therefore is being rejected. The certificate was created during the provisioning process. The troubleshooting steps in [Determining whether the Cloud Load Balancer is configured for a hostname](/apigee/docs/api-platform/fundamentals/environmentgroups-working-with#determining-whether-the-cloud-load-balancer-is-configured-for-a-hostname) show you how to locate and inspect the certificate.\n- If you're unable to resolve the problem, contact the person who provisioned Apigee for further assistance.\n\n\nIn the next step, you will change the target endpoint of the API proxy.\n[1](/apigee/docs/api-platform/get-started/create-proxy) [2](/apigee/docs/api-platform/get-started/deploy-proxy) [3](/apigee/docs/api-platform/get-started/test-proxy) [(NEXT) Step 4: Change the target endpoint](/apigee/docs/api-platform/get-started/change-endpoint) [5](/apigee/docs/api-platform/get-started/add-policy)\n\n\u003cbr /\u003e"]]
