For what purpose do you want the OAS documents to be stored within Apigee? Are these used within the OASValidation step? If so, you can attach such specifications to the API proxy itself, under /resources/oas . Place .yaml or .json OAS documents there, in the bundle.
You also have the option to attach these to the environment or to the organization, too, using the administrative API. For X or hybrid, Use this URL:
The downside of this is, at the current moment, these resource files are not accessible from the Apigee UI. As an operator or admin, you can’t “see them” by clicking through the UI. There are a bunch of things in Apigee that you can manage at th environment scope - keyvalue maps, truststores, references, target servers, and so on - and you can see all of those things in the UI. But at the moment you cannot administer or view the resourcefiles.
We are using APIGEE Edge (SaaS) and yes they are used during validation. We use https://github.com/geraintluff/tv4 to validate the incoming data against spec.
Can you confirm if the same curl command would be applicable for APIGEE Edge (SaaS)?