Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Generating OpenAPI Specification documentation for application-specific REST APIs

Updated on November 23, 2022

You can list service packages that contain REST services in your application rule to include their OpenAPI Specification (OAS) documentation in your application's OAS documentation. All of the services that you list are documented together in a single application OAS landing page, which you can view in the application's API channel.

Before you begin: To ensure that you generate accurate and useful OAS documentation, review the Best practices for generating OpenAPI Specification documentation.
  1. In the header of Dev Studio, click the name of the application, and then click Definition.
  2. On the Application form, click the Integration & security tab.
  3. In the Service Packages section, select the service packages that you want to document:
    • To add a package, click the Add item icon, and then select a service package from the list.
    • To remove a service package, in the row for that service package, click the Delete icon.
  4. Click Save.
What to do next: Confirm that the OAS documentation for the REST services included in your service package was generated. For more information, see Viewing application-specific REST APIs.
  • Previous topic Best practices for generating OpenAPI Specification documentation
  • Next topic Viewing application-specific REST APIs

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us