Parabéns! Você configurou uma organização da Apigee com faturamento de pagamento por utilização.
Você precisa concluir duas tarefas importantes ao iniciar sua jornada com a Apigee:
Na Visão geral, é possível testar o ambiente de execução da Apigee de ponta a ponta implantando um proxy de amostra e enviando uma solicitação
de teste para o proxy.
Implantar o proxy de amostra
Clique em Implantar API no card Testar o ambiente de execução da Apigee para implantar o proxy Hello World de exemplo.
Quando a implantação for concluída, o card vai mostrar as etapas para enviar uma solicitação de teste.
Uma solicitação bem-sucedida retorna a string: Hello, Guest!. Se a solicitação não for bem-sucedida, consulte Solução de problemas.
Configure e teste uma entrada de DNS para seu host. Crie uma entrada DNS usando um dos
seguintes métodos:
No registrador, crie um registro A que aponte o nome do host do grupo de ambientes para
o endereço IP da instância da Apigee. Por exemplo, se o
nome do host for sales.example.com e o IP for 10.23.0.2, aponte o
registro de sales.example.com para o endereço 10.23.0.2.
Use o Google Cloud DNS para mapear um URL para um endereço IP.
Quando a configuração do DNS for concluída, envie uma solicitação de teste para o proxy usando o seguinte comando:
curl https://EXTERNAL_IP/helloworld
Em que EXTERNAL_IP é o endereço IP externo da instância. Exemplo:
curl https://35.244.227.125/helloworld
Uma solicitação bem-sucedida retorna a string: Hello, Guest!. Se a solicitação não for bem-sucedida, consulte Solução de problemas.
É possível usar o Google Cloud Identity and Access Management (IAM) para conceder permissões a desenvolvedores ou outros colaboradores para
acessar e gerenciar seu programa de API. Para mais informações sobre como usar o IAM para definir quem tem qual acesso a qual recurso na
implementação da Apigee, consulte Visão geral do IAM.
Próximas etapas
Faça um tour pelos tutoriais da Apigee, incluindo:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 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,["# Recommended next steps\n\n*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----------------------------\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\n### Deploy 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\n### Call 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\n### Call 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--------------------------------------\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\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)."]]