Create a Service from the Services Catalog. The general properties that you specify when creating a Service include:

• Project: The project to save the Service in. The project location and its settings determines who on the development team can view and edit the Service. Refer to Assign project permissions for more information.
• Name: The Service name. This name is visible in the DeveloperHub as the Service name.
• URL Slug: A value to identify the Service. The URL Slug becomes part of the endpoint URLS and should be unique in the environment (Org).
• Service Version: Specify your own value. The version also becomes part of endpoint URLs.
• Tags: Optional tags that display in the DeveloperHub.
• Servers: The OAS 3.x specification allows for multiple servers. You can select Snaplexes at the Service or the endpoint level.
• Description: Describes the Service and displays in the DeveloperHub.

Resources associated with the Service are available from tabs:

• Endpoints: The access points that make functionality available to consumers. Each endpoint is a collection of paths that map to one upstream native or external resource.
  Tip: To quickly view or navigate to an endpoint, click the down arrow on the first endpoint. The remaining endpoints and the supported HTTP methods display:
  

  

  
  
• Policies: The Policies that apply at the catalog, Service, or endpoint level.
• Assets: Assets such as pipelines, accounts, or tasks that you create in Classic Manager in the Service project folder.
• Documentation: To enhance the visibility of the Service in the DeveloperHub, you can select the categories it displays under and add images. You can also add images and explanatory text in Markdown format that the Portal renders in HTML.

The following describe how to perform tasks related to Services:

• Create a Service
• Create a Catalog Policy
• Apply a Policy to a Service
• Test a Service