Service Catalog Open API
-
- UpdatedJan 30, 2025
- 15 minutes to read
- Yokohama
- API reference
The Service Catalog Open API provides endpoints to create and retrieve service specifications.
Use this API to manage service catalog information between external systems and the ServiceNow AI Platform. The Service Catalog Open API is a ServiceNow® implementation of the TM Forum Service Catalog API REST specification. This implementation is based on the TMF633 Service Catalog API REST Specification Version 4, October 2020.
This API is included in the Product Catalog Advanced application, which is available on the ServiceNow Store.
This API is provided within the sn_prd_pm_adv
namespace.
The calling user must have the sn_prd_pm_adv.catalog_integrator role.
- Characteristic [sn_prd_pm_characteristic]
- Characteristic Option [sn_prd_pm_characteristic_option]
- Service Specification [sn_prd_pm_service_specification]
- Specification Relationship [sn_prd_pm_specification_relationship]
Service Catalog Open - GET /servicespecification
Retrieves a list of all service specifications.
URL format
Default URL: /api/sn_prd_pm_adv/catalogmanagement/servicespecification
Supported request parameters
Name | Description |
---|---|
None |
Name | Description |
---|---|
None |
Headers
The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.
Header | Description |
---|---|
None |
Status codes
The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.
Response body parameters (JSON)
Example: cURL request
This example retrieves all service specifications.
Response body.
Service Catalog Open - GET /servicespecification/{specificationId}
Retrieves a service specification.
URL format
Default URL: /api/sn_prd_pm_adv/catalogmanagement/servicespecification/{specificationId}
Supported request parameters
Name | Description |
---|---|
specificationId | Sys_id of the service specification to retrieve. Data type: String Table: Service Specification [sn_prd_pm_service_specification] |
Name | Description |
---|---|
fields | List of fields to return in the response. Invalid fields are ignored. If this
parameter is not used, all fields are returned. Data type: String |
state | Filter service specifications by state. Only specifications with a state
matching the value of this parameter are returned in the response. Data type: String |
Name | Description |
---|---|
None |
Headers
The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.
Header | Description |
---|---|
None |
Header | Description |
---|---|
Content-Type | Data format of the response body. Only supports application/json. |
Status codes
The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.
Status code | Description |
---|---|
200 | Request successfully processed. |
400 | Bad Request. Could be any of the following reasons:
|
404 | Record not found. Record associated with the ID is not found in the table. |
Response body parameters (JSON)
Example: cURL request
This example retrieves a service specification for a firewall service.
Response body.
Service Catalog Open - POST /servicespecification
Creates a service specification.
URL format
Default URL: /api/sn_prd_pm_adv/catalogmanagement/servicespecification
Supported request parameters
Name | Description |
---|---|
None |
Name | Description |
---|---|
None |
Headers
The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.
Header | Description |
---|---|
Accept | Data format of the response body. Only supports application/json. |
Content-Type | Data format of the request body. Only supports application/json. |
Header | Description |
---|---|
Content-Type | Data format of the response body. Only supports application/json. |
Status codes
The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.
Status code | Description |
---|---|
201 | Request successfully processed. |
400 | Bad Request. Could be any of the following reasons:
|
Response body parameters (JSON)
Example: cURL request
This example creates a service specification for a firewall service.
Response body.