Pastikan project Google Cloud yang sama tempat Anda membuat proxy API dipilih
dari dropdown di bagian atas halaman.
Pilih tab Grup Lingkungan.
Dalam tabel, cari baris untuk grup lingkungan yang berisi lingkungan tempat
myproxy di-deploy. Nama host muncul di kolom Nama Host pada baris ini. Contoh: mydomain.com.
Panggil proxy API. Cara Anda memanggil proxy bergantung pada apakah instance Apigee Anda dikonfigurasi untuk akses jaringan eksternal atau internal.
Jika Anda tidak yakin bagaimana konfigurasi instance Apigee Anda, hubungi administrator Apigee Anda.
Akses eksternal: Jika instance Apigee Anda dikonfigurasi untuk akses eksternal,
panggil proxy sebagai berikut:
curl https://YOUR_ENV_GROUP_HOSTNAME/myproxy
Dengan YOUR_ENV_GROUP_HOSTNAME adalah nama host yang Anda dapatkan di
langkah sebelumnya.
Contoh:
curl https://mydomain.com/myproxy
Berikut contoh lain, dengan layanan DNS karakter pengganti nip.io digunakan untuk host:
curl https://198.51.100.251.nip.io/myproxy
Akses internal: Jika instance Apigee Anda dikonfigurasi untuk akses jaringan internal, beberapa langkah tambahan diperlukan
untuk mendapatkan akses ke load balancer internal dan alamat IP-nya. Untuk mengetahui detailnya, lihat Memanggil proxy dengan akses khusus internal.
Panggilan yang berhasil ke proxy akan menampilkan output berikut:
Pastikan project Google Cloud yang sama tempat Anda membuat proxy API dipilih
dari dropdown di bagian atas halaman.
Di UI Konsol Cloud, pilih Admin > Environments > Groups.
Klik Lihat di konsol Google Cloud .
Pilih tab Grup Lingkungan.
Dalam tabel, cari baris untuk grup lingkungan yang berisi lingkungan tempat myproxy di-deploy. Nama host muncul di kolom Nama Host pada baris ini. Contoh: mydomain.com.
Panggil proxy API. Cara Anda memanggil proxy bergantung pada apakah instance Apigee Anda dikonfigurasi untuk akses jaringan eksternal atau internal.
Jika Anda tidak yakin bagaimana konfigurasi instance Apigee Anda, hubungi administrator Apigee Anda.
Akses eksternal: Jika instance Apigee Anda dikonfigurasi untuk akses eksternal,
panggil proxy sebagai berikut:
curl https://YOUR_ENV_GROUP_HOSTNAME/myproxy
Dengan YOUR_ENV_GROUP_HOSTNAME adalah nama host yang Anda dapatkan di
langkah sebelumnya.
Contoh:
curl https://mydomain.com/myproxy
Berikut contoh lain, dengan layanan DNS karakter pengganti nip.io digunakan untuk host:
curl https://198.51.100.251.nip.io/myproxy
Akses internal: Jika instance Apigee Anda dikonfigurasi untuk akses jaringan internal, beberapa langkah tambahan diperlukan
untuk mendapatkan akses ke load balancer internal dan alamat IP-nya. Untuk mengetahui detailnya, lihat Memanggil proxy dengan akses khusus internal.
Panggilan yang berhasil ke proxy akan menampilkan output berikut:
Jika Anda melihat error TLS/SSL, seperti error handshake SSL, hubungi penyedia DNS Anda untuk memastikan data A DNS untuk nama host dikonfigurasi dengan benar. Pastikan data memiliki IP load balancer yang dibuat selama penyediaan Apigee.
Jika Anda tidak yakin dengan IP yang harus digunakan, lihat
Menentukan apakah Cloud Load Balancer dikonfigurasi untuk nama host.
Jika Anda melihat error sertifikat TLS/SSL, sertifikat SSL yang terkait dengan load balancer mungkin tidak memiliki nama host yang benar, dan oleh karena itu ditolak. Sertifikat dibuat selama proses penyediaan.
Langkah-langkah pemecahan masalah di
Menentukan apakah Cloud Load Balancer dikonfigurasi untuk nama host menunjukkan cara
menemukan dan memeriksa sertifikat.
Jika Anda tidak dapat menyelesaikan masalah, hubungi orang yang menyediakan
Apigee untuk mendapatkan bantuan lebih lanjut.
Pada langkah berikutnya, Anda akan mengubah endpoint target proxy API.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 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"]]
