Get published Service versions

GET https://{controlplane_path}/api/1/rest/public/developer_hub/services/versions/published?org_name={org_name}

Returns published Service versions available on the Developer Portal, optionally filtered by category.

Prerequisites

None. This API doesn't require authentication by default.

Note: To get a response from this API, the Allow Access to APIM 3.0 Portal pages without login setting must be enabled on the API Management 3.0 settings page in Admin Manager. If disabled, all pages except the login page require users to log in.

Example

curl -X 'GET' \
  'https://elastic.snaplogic.com/api/1/rest/public/developer_hub/services/versions/published?org_name=my-environment'

With category filtering:

curl -X 'GET' \
  'https://elastic.snaplogic.com/api/1/rest/public/developer_hub/services/versions/published?org_name=my-environment&categories=books&categories=inventory'

Query parameters

Key Type Description
org_name string Required. The name of the environment (Org).
categories array Optional. One or more category names to filter the results (for example, categories=books&categories=inventory).

Request header

None required unless the Developer Portal requires authentication.

Request body

None.

Response


{
  "response_map": {
    "entries": [
      {
        "version_name": "1.0",
        "version_snid": "abc123def456",
        "service_name": "BookStore API",
        "tags": ["books", "inventory"],
        "description": "Bookstore service for managing inventory",
        "documentation": {}
      }
    ]
  },
  "http_status_code": 200
}
        
Key Type Description
entries array The list of published Service versions.
version_name string The version identifier.
version_snid string The unique snode ID for the Service version.
service_name string The name of the parent Service.
tags array Tags assigned to the Service version.
description string The Service version description.
documentation object The documentation attached to the Service version.

Error handling

HTTP status codes Message Resolution
401 Authorization required The Developer Portal requires authentication. Include an authorization header in the request.
404 Not Found Verify that org_name is correct and the environment exists.