Apigee Lab 1: Generating an API Proxy Using an OpenAPI Specification Reviews
Loading...
No results found.

Google Cloud Skills Boost

Apply your skills in Google Cloud console

Apigee Lab 1: Generating an API Proxy Using an OpenAPI Specification Reviews

11452 reviews

Yerson Z. · Reviewed 11 months ago

Rahul k. · Reviewed 11 months ago

good

Farhan S. · Reviewed 11 months ago

lakshya t. · Reviewed 11 months ago

I believe the lab did not explain many pain points. I ended the lab with status 404 error still I did not find anywhere explained how to resolve it. I used tools like reverse proxy but not explaination

Zacarias V. · Reviewed 11 months ago

SSM S. · Reviewed 11 months ago

nice

irfanmoinuddin m. · Reviewed 11 months ago

Agustina L. · Reviewed 11 months ago

Rick P. · Reviewed 11 months ago

Hesham M. · Reviewed 11 months ago

Nas N. · Reviewed 11 months ago

Gabriel D. · Reviewed 11 months ago

Carlos B. · Reviewed 11 months ago

Pedro S. · Reviewed 11 months ago

Camilo H. · Reviewed 12 months ago

Nikolaus L. · Reviewed 12 months ago

Lakshhya B. · Reviewed 12 months ago

Gayathri D. · Reviewed 12 months ago

Luis T. · Reviewed 12 months ago

Ivan G. · Reviewed 12 months ago

Betty G. · Reviewed 12 months ago

Valentina T. · Reviewed 12 months ago

Sarthak G. · Reviewed 12 months ago

Sandip C. · Reviewed 12 months ago

Base URL Mismatch: The OpenAPI spec specifies the base URL as https://gcp-cs-training-01-test.apigee.net/training/db, but your curl command uses https://eval.example.com/retail/v1. These base URLs need to match for the API to function correctly. Case Sensitivity: The path you are calling is /Categories, but the OpenAPI spec defines it as /categories (all lowercase). The paths in URLs are case-sensitive, so this mismatch could cause a 404 error.

Lily H. · Reviewed 12 months ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.