API / APIGEE Gateway Interview Questions
How do you import an OpenAPI specification into Apigee to generate a proxy?
Apigee can auto-generate an API proxy skeleton directly from an OpenAPI Specification (OAS 3.x or Swagger 2.0). This generates the proxy's flow structure, conditional flows for each operation, and basic passthrough routing - saving significant scaffolding time.
# Method 1: Apigee UI (simplest) # Develop > API Proxies > + Create > Reverse proxy > OpenAPI Spec # Paste or upload the OpenAPI spec # Apigee generates: # - ProxyEndpoint with one ConditionalFlow per operation # - TargetEndpoint pointing to the servers[0].url from the spec # - Basic passthrough proxy (no security policies added yet) # Method 2: apigeecli apigeecli apis create oas \ --name orders-api \ --oas-base-folderpath ./specs/ \ --env prod \ --org my-org \ --token $(gcloud auth print-access-token) # Method 3: Apigee Management API curl -X POST \ "https://apigee.googleapis.com/v1/organizations/my-org/apis?action=import" \ -H "Authorization: Bearer $(gcloud auth print-access-token)" \ -F "file=@proxy-bundle.zip" # What the generated proxy includes: # - One ConditionalFlow per API operation (path + verb) # - Correct basepath from the spec # - TargetEndpoint pointing to spec servers URL # - Does NOT include: # - Security policies (add VerifyAPIKey/OAuthV2 manually) # - Rate limiting (add Quota/SpikeArrest manually) # - Error handling (add FaultRules manually) # Best practice: use OAS generation as a starting point, # then add security and policies to the generated bundle
More Related questions...