Runtime APIs

---
title: Runtime APIs
description: ServiceNow CPQ provides a set of APIs for building front-end applications and manipulating configurations. These are the buyside or runtime APIs that customers and end users can use to create, update, and save ServiceNow CPQ configurations.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/order-management/logik\_io\_runtime\_apis.html
release: brazil
topic_type: concept
last_updated: "2026-03-12"
reading_time_minutes: 7
keywords: [Runtime APIs]
breadcrumb: [API overview and resources, ServiceNow CPQ Configurator, Configure, price, quote apps, Configure, Sales Customer Relationship Management]
---

# Runtime APIs

ServiceNow CPQ provides a set of APIs for building front-end applications and manipulating configurations. These are the buyside or runtime APIs that customers and end users can use to create, update, and save ServiceNow CPQ configurations.

Runtime APIs support the standard create, read, update, and delete functions for ServiceNow CPQ configurations, along with the ability to retrieve bill of materials \(BOM\) data from ServiceNow CPQ.

ServiceNow CPQ provides accessible runtime APIs and a quick start for developers through open source repositories containing API collections that can be imported and tested.

## Runtime API setup

The base URL format for all runtime API calls is `https://<tenant>.<sector>.<cpq>/api/`. The `<tenant>` is the listed tenant name and `<sector>` is the appropriate sector where the environment is located \(usually `test` or `prod`\).

Find the ServiceNow CPQ tenant URL in Salesforce by navigating to **Setup**, searching for **Custom Settings** in the **Quick Find** box, and then selecting **Manage** next to ServiceNow CPQ Tenant.

Runtime API calls are authenticated through a combination of a bearer token and the defined origin in the runtime client. The origins of the runtime application are set when a runtime client is created in the ServiceNow CPQ **Admin** settings.

Add two headers to each request to authorize these API calls as mentioned in the following table:

|Header|Key|Value|
|------|---|-----|
|Origin Header|origin|&lt;runtimeClientOrigin&gt;|
|Authorization Header|authorization|Bearer &lt;runtimeToken&gt;|

Sample headers:

-   origin: localhost
-   authorization: Bearer vEqzz4BVkb15Le11En8axEuN71FA6Vt\_cw

## Create a configuration

The create configuration call passes the ID of the configurable product and receives in response a ServiceNow CPQ configuration ID that can be used to specify this configuration in later calls.

<table id="table_mtd_mls_mhc"><tbody><tr><td>

HTTP method

</td><td>

POST

</td></tr><tr><td>

URL

</td><td>

https://&lt;tenant&gt;.&lt;sector&gt;.logik.io/api/

</td></tr><tr><td>

Path parameters

</td><td>

N/A

</td></tr><tr><td>

Query parameters

</td><td>

N/A

</td></tr></tbody>
</table>The two key pieces of the payload are:

-   The ID of a ServiceNow CPQ enabled product, with a blueprint that is deployed
-   The ServiceNow CPQ configuration UUID that is being reconfigured

Sample URL:

`https://dev1.test.cpq/api/`

Sample payload:

```
{
  "sessionContext": 
  { 
    "stateful": true
  },
  "partnerData": 
  { 
    "product":
    {
      "configuredProductId": "<Id of a Logik.io Enabled Product>", 
    }
  },
  "fields": []
}
```

**Note:** You can also initialize the configuration by passing field values to the fields array in the following format:

```
{
  "variableName": "<Field Name>", "value": "<Field Value>"
}
```

Sample response:

```
{
  "fields": [<ARRAY OF FIELD OBJECTS>],
  "uuid": "08176434-9b1e-4fc8-b2c4-8aba2c35fda3", 
  "revision": 0,
  "relatedChanges": 
  [
    {
      "key": "products",
      "type": "PRODUCT"
    }
  ],
  "valid": true, 
  "messages": [], 
  "productChange": true,
  "products": [<ARRAY OF PRODUCTS IN CONFIGURATION>],
  "total": 30,
  "layouts": [<ARRAY OF LAYOUTS>]
}
```

## Reconfigure a configuration

The reconfigure API call is similar to the create configuration call. The reconfigure call passes the ID of the configurable product and an existing ServiceNow CPQ configuration ID. In return, it receives a new Configuration ID with the same field data as the prior configuration but allows changes to be made.

**Note:** The **UUID** field in the response payload contains the new ServiceNow CPQ configuration ID. Use the new configuration ID for all operations going forward in the reconfiguration process, including update, save, and retrieve BOM.

<table id="table_vtd_mls_mhc"><tbody><tr><td>

HTTP method

</td><td>

POST

</td></tr><tr><td>

URL

</td><td>

https://&lt;tenant&gt;.&lt;sector&gt;.logik.io/api/

</td></tr><tr><td>

Path parameters

</td><td>

N/A

</td></tr><tr><td>

Query parameters

</td><td>

N/A

</td></tr></tbody>
</table>The two key pieces of the payload are:

-   The ID of a ServiceNow CPQ enabled product, with a blueprint that is deployed
-   The ServiceNow CPQ configuration UUID that is being reconfigured

Sample URL:

`https://dev1.test.Logik/api/`

Sample payload:

```
{
  "sessionContext": 
  { 
    "stateful": true
  },
  "partnerData": 
  { 
    "product": 
    {
      "configuredProductId": "<Id of a Logik.io Enabled Product>", 
      "configurationAttributes": 
      {
        "LGK__ConfigurationId__c": "<uuid>"
      }
    }
  },
  "fields": []
}
```

Sample response:

```
{
  "fields": [<ARRAY OF FIELD OBJECTS>],
  "uuid": "d98d60cd-9379-4b7b-86fd-de828c340f80", 
  "revision": 0,
  "relatedChanges": 
  [
    {
      "key": "products",
      "type": "PRODUCT"
    }
  ],
  "valid": true, 
  "messages": [], 
  "productChange": true,
  "products": [<ARRAY OF PRODUCTS IN CONFIGURATION>],
  "total": 30,
  "layouts": [<ARRAY OF LAYOUTS>]
}
```

## Update a configuration

Updating a configuration requires a configuration to be loaded using either the create configuration or reconfigure API calls. The update configuration call passes a ServiceNow CPQ Configuration ID and any desired field values, and in response, receives the updated configuration from ServiceNow CPQ.

<table id="table_pwh_rts_mhc"><tbody><tr><td>

HTTP method

</td><td colspan="4">

PATCH

</td></tr><tr><td>

URL

</td><td colspan="4">

https://&lt;tenant&gt;.&lt;sector&gt;.cpq/api/

</td></tr><tr><td>

Path parameters

</td><td colspan="4">

N/A

</td></tr><tr><td rowspan="3">

Query Parameters

</td><td>

Name

</td><td>

Allowed Value

</td><td>

Required?

</td><td>

Default if not specified

</td></tr><tr><td>

delta

</td><td>

true \| false

</td><td>

optional

</td><td>

true

</td></tr><tr><td>

save

</td><td>

true \| false

</td><td>

optional

</td><td>

false

</td></tr></tbody>
</table>Query parameters:

**delta**

If **delta=true**, ServiceNow CPQ sends back only data that has changed based on the update that was sent. This is the default behavior.

If **delta=false**, ServiceNow CPQ sends back the entire configuration and BOM data in response.

**SAVE**

-   If **save=true**, ServiceNow CPQ saves the configuration and sends the data to a webhook or writing the data into custom objects in Salesforce. This is the behavior of the save configuration call.
-   If **save=false**, ServiceNow CPQ updates this configuration and sends the updated data back in the response. This is the default behavior, and this is the behavior of the update call.

Sample URL:

`https://dev1.test.logik.io/api/fbc3d32c-7f86-4461-b144-986a0e8a5768`

Sample payload:

```
{
  "fields": 
  [
    {
      "variableName": "orderQty", 
      "value": 3
    }
  ]
}
```

Sample response:

```
{
  "fields": [],
  "uuid": "fbc3d32c-7f86-4461-b144-986a0e8a5768", 
  "revision": 0,
  "relatedChanges": 
  [
    {
      "key": "products",
      "type": "PRODUCT"
    }
  ],
  "valid": true, 
  "messages": [], 
  "productChange": true, 
  "products": null
}
```

## Save a configuration

Saving a configuration is a subset of the update configuration. It requires a configuration to be loaded using either the create configuration or reconfigure API calls. The save configuration call passes a ServiceNow CPQ configuration ID and any desired field values, and in response, receives the updated configuration from ServiceNow CPQ.

**Note:** The only difference between a normal update call and a save call is the addition of the query parameter **save=true** in the URL. If set to false or excluded, this is a normal update call.

If the save API is called in the Salesforce backend then ServiceNow CPQ asynchronously creates and populates the custom objects 'Configuration Field Data Sets' and 'Configuration Line Items' with the appropriate data.

If your ServiceNow CPQ instance has a webhook configured, when the save API is called, the data is sent to the endpoint specified in the webhook setting. See [Webhooks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/order-management/cpq-webhooks.md).

**Note:** This ends the configuration session. Further edits or updates to the configuration must be started from the create configuration or reconfigure API calls.

<table id="table_mrm_2ss_mhc"><tbody><tr><td>

HTTP method

</td><td colspan="4">

PATCH

</td></tr><tr><td>

URL

</td><td colspan="4">

https://&lt;tenant&gt;.&lt;sector&gt;.cpq/api/

</td></tr><tr><td>

Path parameters

</td><td colspan="4">

N/A

</td></tr><tr><td rowspan="3">

Query Parameters

</td><td>

Name

</td><td>

Allowed Value

</td><td>

Required?

</td><td>

Default if not specified

</td></tr><tr><td>

delta

</td><td>

true \| false

</td><td>

optional

</td><td>

true

</td></tr><tr><td>

save

</td><td>

true \| false

</td><td>

optional

</td><td>

false

</td></tr></tbody>
</table>Query parameters:

**delta**

If **delta=true**, ServiceNow CPQ sends back only data that has changed based on the update that was sent. This is the default behavior.

If **delta=false**, ServiceNow CPQ sends back the entire configuration and BOM data in response.

**save**

If **save=true**, ServiceNow CPQ saves this configuration and \(depending on the settings\) performs additional actions such as sending the data to a webhook or writing the data into custom objects in Salesforce.

If **save=false**, ServiceNow CPQ updates this configuration and sends the updated data back in the response. This is the behavior of the update call.

Sample cURL request:

```
curl --location --request PATCH 'https://mpanigrahi-demo.demo01.logik.io/api/6d0ef6fd-4c88-44f3-a296-b03421c369c6' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Origin: https://mpanigrahi-demo.demo01.logik.io' \
--header 'Authorization: <<RUNTIME TOKEN>>' \
--header 'Cookie: LGKSESSION=NDA5OWJmNmEtNDhhOS00YTc4LTk3ODktZTg0OGYyOGIwMjZk' \
--data '{"fields":[{"variableName":"name_d1","value":"megha","dataType":"text"}],"responseState":{"setPagination":{"collections":{"pageSize":10,"pageNumber":0},"fields":{"pageSize":10,"pageNumber":0},"componentTypes":{"pageSize":10,"pageNumber":0}},"defaultPagination":{"pageSize":10,"pageNumber":0},"searchValues":{}}}'
```

Sample response:

```
{
"fields": [<ARRAY OF FIELD OBJECTS>],
"uuid": "8817655d-7a11-41ef-a9fd-59c2855a3e4b", 
"revision": 1,
"valid": true, 
"messages": [], 
"productChange": false,
"products": [<ARRAY OF PRODUCTS IN CONFIGURATION>],
"total": 0
}
```

## BOM APIs

The BOM APIs are useful for retrieving the final output of configuration. You can use the BOM APIs to retrieve the entire BOM, or specific subsets, such as sales or manufacturing BOMs.

The Get BOM call passes a ServiceNow CPQ Configuration ID and in return receives the current BOM generated by the current state of the configuration. There are 3 built in BOM types: "all", "sales" and "manufacturing". You can dynamically add additional BOM types by setting the **bomType** field on the product.

**Note:** If the BOM type is not included, the API returns the entire BOM.

<table id="table_dvd_mls_mhc"><tbody><tr><td>

HTTP method

</td><td colspan="3">

GET

</td></tr><tr><td>

URL

</td><td colspan="3">

https://&lt;tenant&gt;.&lt;sector&gt;.cpq/api/&lt;uuid&gt;/bom/&lt;bomType&gt;

</td></tr><tr><td rowspan="3">

Path Parameters

</td><td>

Name

</td><td>

Allowed Value

</td><td>

Required?

</td></tr><tr><td>

&lt;uuid&gt;

</td><td>

32 character ServiceNow CPQ configuration UUID

</td><td>

required

</td></tr><tr><td>

&lt;bomType&gt;

</td><td>

name of the BOM to retrieve

</td><td>

optional

</td></tr><tr><td>

Query parameters

</td><td colspan="3">

N/A

</td></tr></tbody>
</table>Sample response:

```
{"products": [
        {
            "id": "01t5f000006QKysAAG",
            "quantity": 1,
            "bomType": "Sales",
            "orderNumber": 10,
            "type": "accessory",
            "name": "Amend Flow Bundle Sub",
            "partnerId": "01t5f000006QKysAAG",
            "productCode": "AFBC-SC",
            "externalId": "",
            "productFamily": "Miscellaneous",
            "description": "",
            "uom": "",
            "price": 5,
            "extPrice": 5,
            "level": 0,
            "rollUpPrice": 5
        },
        {
            "id": "01t5f000006QKz2AAG",
            "quantity": 1,
            "bomType": "Sales",
            "orderNumber": 20,
            "type": "accessory",
            "name": "Amend Flow Bundle Asset",
            "partnerId": "01t5f000006QKz2AAG",
            "productCode": "AFBC2-SC",
            "externalId": "",
            "productFamily": "Miscellaneous",
            "description": "",
            "uom": "",
            "price": 25,
            "extPrice": 25,
            "level": 0,
            "rollUpPrice": 25
        }
    ]}
```

For information about additional configuration APIs and sample scenarios, see [Additional configuration APIs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/order-management/logik_io_additional_configuration_apis.md).