---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# API overview and resources

# API overview and resources {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Learn about the APIs that are available in CPQ to manage configurations.

CPQ provides APIs for both the end user (runtime) for configurations and the administrative side for setup and management.

The runtime APIs support the standard create, read, update, and delete functions for CPQ configurations, along with the ability to retrieve bill of materials (BOM) data from CPQ. These APIs can be used to build a headless or custom UI for end users to create CPQ configurations.

Administrative APIs can be used to work with blueprints, fields, sets, product pickers, rules, managed tables, and the Matrix Loader for imports and exports. The admin APIs can be integrated or automated to perform routine tasks
like data migration.

## API resources {#api_overview_and_resources__api_resources}

The following resources can help you get started with CPQ APIs.

To view a Github repository with OpenAPI specifications and Postman collections for CPQ APIs, see:

[API Documentation](https://github.com/logikioopensource/API-Documentation)

For interactive and explorable API documentation with code examples for both runtime and admin APIs, see:

[CPQ API Reference](https://api-docs.logik.io/#introduction)

## Authenticating API calls {#api_overview_and_resources__authenticating_api_calls}

Runtime API calls are authenticated using runtime client tokens defined in CPQ Admin. For more information about runtime API calls and runtime client tokens, see:

[Intro to runtime API calls](https://servicenow-prod.fluidtopics.net/KwcDlqRaTMDk~lQO4yliIQ "Runtime, or buyside, APIs are used to create, update, and save configurations.")

Administrative API calls are authenticated with admin API tokens that are also set up in CPQ Admin. For more information about admin API tokens and permissions, see:

[Intro to admin API keys](https://servicenow-prod.fluidtopics.net/~K9nCCkk5Pb4h_IrY6yK1A "You can use admin API calls to access Admin functionality without using the Admin UI interface and a browser.")
**Zugehörige Konzepte**   

* [Runtime APIs](https://servicenow-prod.fluidtopics.net/hETgrfKXw2Mtj3Lju5W4wQ "Runtime APIs")
* [Authenticating CPQ API calls](https://servicenow-prod.fluidtopics.net/IWmWmIxQiFgPhBHInQ_t9w "Secure CPQ API calls with admin API keys, JWT tokens, session cookies, or Google IdP for runtime and Admin tasks.")
* [Additional configuration APIs](https://servicenow-prod.fluidtopics.net/BFoCVncZF3iNymUQr65ZWg "These CPQ configuration APIs let you retrieve or delete an existing configuration. They complement the runtime APIs and are useful for viewing full configuration details and for removing configurations no longer needed. Use them alongside the standard create, update, reconfigure, and BOM APIs to support end-to-end configuration workflows.")
* [Admin APIs: Blueprint import and export](https://servicenow-prod.fluidtopics.net/On6RpQAowPt8e_1yrqSffw "You can export a blueprint to back it up, or export and import a blueprint to move it from one CPQ environment to another.")
* [Admin APIs: Managed tables](https://servicenow-prod.fluidtopics.net/pnKdWDCWJ6roCSOtQ~OHJg "Legacy information about APIs that interact with managed tables")