OpenAPI Specs for Salesforce REST APIs

I ran this in my simple org and came up with a spec that's close to 700K lines.   I need to be able to give out a simple spec focusing on just specific objects.  700K is too big to even filter without a lot of work.      

 The Salesforce REST API supports external IDs in virtually every place Ids are used.    For a non-Salesforce developer (who is typically someone you'd create OpenAPI spec for), this is probably the only form of the REST calls they would use.   Yet you don't include them anywhere in the generated document.       Any plans to support this?     FYI - Here's a reference to the REST API Guide in case you are not familiar with how they fit into the API:  https://MyDomainName.my.salesforce.com/services/data/v63.0/sobjects/Merchandise__c/MerchandiseExtID__c/123 -H "Authorization: Bearer token"

External teams calling a Salesforce API would ideally like to see the possible values for each field.   

I was able to use this for a standard object(ContentVersion) and it worked fine. For the POST request it showed a lot of fields without the create() property so I had to clean it up. 

When I ran it for a custom object though it came back empty. I double checked that the user that was authorized has access to it.

Hi Team,

We are trying to do POC and before we do that just wanted to check if there is any tentative data for this feature to be Generally available.

Thanks in advance.

Regards,

Sushil

Hi Community, 

we want to define one or more custom apex rest services which we want in a first step define in an open api specification. Is there a possibility to use this defined spec somehow in Salesforce to generate some parts of it, or are there any useful tips which tool to use for the definition? This will be our first approach 

I've confirmed the enablement of the Beta feature in the User Interface configuration screen.

I'm making a request for the OAS using this command:

curl -vvv -H "Content-Type: text/plain" -d '{"resources" : ["*"]}' https://redacted.develop.my.salesforce.com/services/data/v61.0/async/specifications/oas3

• `v61.0` because the docs say to specify the latest version
• `-H "Content-Type: text/plain"` because I found another post saying it shouldn't be the default that curl sends, `Content-Type: application/x-www-form-urlencoded`
• `-vvv` shows `POST /services/data/v61.0/async/specifications/oas3 HTTP/2`

The response is:

[{"errorCode":"NOT_FOUND","message":"The requested resource does not exist"}]

Using `v60.0` produces a different response:

[{"message":"Session expired or invalid","errorCode":"INVALID_SESSION_ID"}]

I don't know what more to try. Does the request require an `Authorization` header?

Hi,

Feedback has been provided in this Community for specific items; e.g. generate OAS for Apex REST endpoints.  I would like to understand the use cases you are using the Beta with.  What problem are you solving using OAS?  Why do you need OAS?  How you are using the generated OAS?  With client library generators, and if so, which ones?  To generate documentation?  To import into API clients such as Postman?  Any thoughts on the generated OAS - what do you like and don't like about it?  Please share any details you can.  If you would be more comfortable sharing privately, then please reach out to me directly.

Thanks,

Jeremy