¡Felicitaciones! Configuraste correctamente una organización de Apigee con facturación de pago por uso.
Hay dos tareas importantes que debes completar cuando comiences tu recorrido con Apigee:
Prueba el entorno de ejecución de extremo a extremo
En la descripción general, puedes probar tu entorno de ejecución de Apigee de extremo a extremo si implementas un proxy de muestra y luego envías una solicitud de prueba al proxy.
Implementa el proxy de muestra
Haz clic en Implementar API en la tarjeta Prueba tu entorno de ejecución de Apigee para implementar el proxy Hello World de muestra.
Cuando se completa la implementación, en la tarjeta se muestran los pasos para enviar una solicitud de prueba.
El proxy puede tardar hasta un minuto en implementarse.
Una solicitud correcta muestra la string: Hello, Guest! Si tu solicitud no funciona, consulta Solución de problemas.
Configura y prueba una entrada de DNS para el host. Crea una entrada de DNS mediante uno de los
siguientes métodos:
En tu registrador, crea un registro A que dirija el nombre de host del grupo de entornos a la dirección IP de tu instancia de Apigee. Por ejemplo, si el nombre de host es sales.example.com y la IP es 10.23.0.2, dirige el registro de sales.example.com a la dirección 10.23.0.2.
Usa Google Cloud DNS para asignar una URL a una dirección IP.
Una vez que se complete la configuración de DNS, envía una solicitud de prueba al proxy con el siguiente comando:
curl https://EXTERNAL_IP/helloworld
donde EXTERNAL_IP es la dirección IP externa de la instancia. Por ejemplo:
curl https://35.244.227.125/helloworld
Una solicitud correcta muestra la string: Hello, Guest! Si tu solicitud no funciona, consulta Solución de problemas.
Puedes usar Cloud Identity and Access Management (IAM) para otorgar permisos a desarrolladores o a otros colaboradores a fin de que accedan y administren tu programa de API. Si quieres obtener más información sobre el uso de IAM para definir quién tiene qué acceso a qué recurso en la implementación de Apigee, consulta Descripción general de IAM.
Próximos pasos
Haz un recorrido por los instructivos de Apigee, incluidos los siguientes:
[[["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-08-07 (UTC)"],[[["\u003cp\u003eThis guide focuses on setting up and testing an Apigee organization with Pay-as-you-go billing, specifically for Apigee, not Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eAfter setting up, users can test their Apigee runtime by deploying a sample "Hello World" proxy and sending a test request.\u003c/p\u003e\n"],["\u003cp\u003eThe test request method varies depending on whether you configured external or internal access during setup, with specific instructions provided for each.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers and collaborators can be granted access to manage the API program using Google Cloud Identity and Access Management (IAM).\u003c/p\u003e\n"],["\u003cp\u003eThere are tutorials available that offer further guidance, such as guarding against traffic spikes and getting detailed views of request/response flows.\u003c/p\u003e\n"]]],[],null,["*This page\napplies to **Apigee** , but not to **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nCongratulations! You have successfully set up an Apigee organization with Pay-as-you-go billing!\nThere are two important tasks to complete as you begin your journey with Apigee:\n\n- [Test your runtime end to end](#test-runtime)\n- [Add developers and other collaborators](#add-developers)\n\nTest your runtime end to end\n\nFrom the **Overview**, you can test your Apigee runtime end-to-end by deploying a sample proxy and then sending a test\nrequest to the proxy.\n\nDeploy the sample proxy\n\nClick **Deploy API** on the **Test your Apigee runtime** card to deploy the sample `Hello World` proxy.\nWhen deployment completes, the card displays steps for sending a test request.\n| **Note:**It can take up to a minute for the proxy to deploy.\n\nCall the proxy with external access\n\nIf you selected *external* access in [Step\n4: Configure access routing](/apigee/docs/api-platform/get-started/console-configure-access):\n\n1. Send a test request to the proxy using the following command: \n\n ```scdoc\n curl -H \"Host: EXTERNAL_IP.nip.io\" \\\n https://EXTERNAL_IP/helloworld\n ```\n\n Where \u003cvar translate=\"no\"\u003eEXTERNAL_IP\u003c/var\u003e is the external IP address of your runtime instance. For example: \n\n ```text\n curl -H \"Host: 35.244.227.125.nip.io\" \\\n https://35.244.227.125/helloworld\n ```\n\n A successful request returns the string: `Hello, Guest!` If your request is not successful, see [Troubleshooting](/apigee/docs/api-platform/get-started/troubleshooting-install).\n2. Set up and test a DNS entry for your host. Create a DNS entry using either of the following methods:\n - At your registrar, create an A record pointing your environment group hostname to the IP address of your Apigee instance. For example, if your hostname is `sales.example.com` and the IP is 10.23.0.2, then point the record for `sales.example.com` to the address `10.23.0.2`.\n - Use Google [Cloud DNS](/dns/docs) to map a URL to an IP address.\n3. Once DNS setup is complete, send a test request to the proxy using the following command: \n\n ```scdoc\n curl https://EXTERNAL_IP/helloworld\n ```\n\n Where \u003cvar translate=\"no\"\u003eEXTERNAL_IP\u003c/var\u003e is the external IP address of your runtime instance. For example: \n\n ```text\n curl https://35.244.227.125/helloworld\n ```\n\n A successful request returns the string: `Hello, Guest!` If your request is not successful, see [Troubleshooting](/apigee/docs/api-platform/get-started/troubleshooting-install).\n\nCall the proxy with internal access\n\nIf you selected *internal* access in [Step\n4: Configure access routing](/apigee/docs/api-platform/get-started/console-configure-access), follow the instructions in [Calling an API\nproxy with internal-only access](/apigee/docs/api-platform/get-started/accessing-internal-proxies) to test your proxy.\n\nAdd developers and other collaborators\n\nYou can use Google Cloud Identity and Access Management (IAM) to grant permissions to developers or other collaborators to\naccess and manage your API program. For more information on using IAM to define *who* has *what access* to *which resource* in your Apigee\nimplementation, see the [IAM overview](/iam/docs/overview).\n\nNext steps\n\n- [Take a tour](/apigee/docs/api-platform/get-started/tutorials) of the Apigee tutorials, including:\n - [Guarding against sudden\n traffic spikes](/apigee/docs/api-platform/tutorials/add-spike-arrest).\n - [Getting a detailed view of\n the request/response flow](/apigee/docs/api-platform/tutorials/view-with-trace)."]]
