Test and publish Services

After configuring Service endpoints, test or publish by changing the Service status. The initial status on creation or migration is Unpublished. You can't change the Service status to test or publish it unless validation passes with no errors. Refer to Validation for more information.

Click the status pill next to the Service name to open the status menu. The following statuses are available:


Service statuses

The status determines whether a Service is visible in the DeveloperHub and whether endpoints are usable:

  • Unpublished: Not available in DeveloperHub and not functional. The Service must meet minimal requirements before you can move it to another status.
  • Testing: Not available in DeveloperHub. The Service and all endpoints meet minimal requirements, are functional, and ready to test with the URL and path.
  • Private: Not available in DeveloperHub. Endpoints are functional and can be used by calling the URL.
  • Restricted: Available in DeveloperHub to users with a SnapLogic login who have access to the underlying Service.
  • Public: Available in DeveloperHub to all users — those who have a SnapLogic or a DeveloperHub login, assuming the portal is configured to require login.
Important: You can't modify a Service in any published status, private, restricted, or public. You must unpublish it first.

Test an endpoint

You can test an endpoint with a command line tool like cURL or an app like Postman. Copy the URL from the clipboard in the path row:

Paste the URL in the test environment. Add any required parameters and authentication.

Deprecate a Service or Service version

If you plan to end-of-life a version of a Service, enable the Deprecated toggle in the Service or Service version edit dialog. This informs those using the Service that they should plan to migrate to a different version. You can provide details in the Documentation for the Service, such as the cut-off date.

The following describe how to perform tasks related to Services and endpoints: