Recommended next steps

Stay organized with collections Save and categorize content based on your preferences.

Congratulations! You have successfully set up an Apigee organization with Pay-as-you-go billing! What's next?

The Finish setting up Apigee page in the console suggests two important tasks to complete as you begin your journey with Apigee.

Test your runtime end to end

Now 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

To deploy the sample Hello World proxy to an environment in your new runtime instance, click Deploy.

Upon successful deployment, the console displays steps for sending a test request.

Call the proxy with external access

If you selected external access in Step 4: Configure access routing, send a test request to the proxy using the following command: 

curl -H "Host: EXTERNAL_IP.nip.io" \
  https://EXTERNAL_IP/helloworld

Where EXTERNAL_IP is the external IP address of your runtime instance. For example: 

curl -H "Host: 35.244.227.125.nip.io" \
  https://35.244.227.125/helloworld

A successful request returns the string: Hello, Guest! If your request is not successful, see Troubleshooting.

You can 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.

Call the proxy with internal access

If you selected internal access in Step 4: Configure access routing, follow the instructions in Calling an API proxy with internal-only access to test your proxy.

Add developers and other collaborators

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.

Next steps