Congratulations! You have successfully set up an Apigee organization with Pay-as-you-go billing!
There are two important tasks to complete as you begin your journey with Apigee:
From the Overview, you can test your Apigee runtime end-to-end by deploying a sample proxy and then sending a test
request to the proxy.
Deploy the sample proxy
Click Deploy API on the Test your Apigee runtime card to deploy the sample Hello World proxy.
When deployment completes, the card displays steps for sending a test request.
A successful request returns the string: Hello, Guest! If your request is not successful, see Troubleshooting.
Set up and test a DNS entry for your host. Create a DNS entry using either of the
following methods:
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.
Use Google Cloud DNS to map a URL to an IP address.
Once DNS setup is complete, send a test request to the proxy using the following command:
curl https://EXTERNAL_IP/helloworld
Where EXTERNAL_IP is the external IP address of your runtime instance. For example:
curl https://35.244.227.125/helloworld
A successful request returns the string: Hello, Guest! If your request is not successful, see Troubleshooting.
You can use Google Cloud Identity and Access Management (IAM) to grant permissions to developers or other collaborators to
access and manage your API program. For more information on using IAM to define who has what access to which resource in your Apigee
implementation, see the IAM overview.
[[["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."],[[["\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)."]]