As far as I know, Postman does not directly support creating an Open API Specification from the Apigee discovery document: 'https://apigee.googleapis.com/$discovery/rest?version=v1'
But, it can be done using: https://github.com/stackql/google-discovery-to-openapi
Steps:
git clone https://github.com/stackql/google-discovery-to-openapi
npm install
chmod 755 bin/google-discovery-to-openapi.mjs
bin/google-discovery-to-openapi.mjs
It will generate an OAS (3.1) for each of the services, Apigee is in: openapi/googleapis.com/v00.00.00000/services/apigee/apigee.yaml.
Then just import that into Postman!
Once imported, see this blog post to set up authentication via OAuth 2.0. https://blog.postman.com/how-to-access-google-apis-using-oauth-in-postman/
The last step is to set variables so they are used in each of the API calls. I haven't quite figured this part out yet, as the collection uses path parameters like ":organizationsId" and I haven't figured out how to propagate those values down to each of the APIs.
Solved! Go to Solution.
Thankfully, @apickelsimer reminded me that we publish a Postman collection that uses {{ORG_ID}} type variables which can be set in an Environment. The collection is here: https://www.postman.com/dynolab/workspace/apigee-api/overview