Skip to content

The Pricefx Backend API

Pricefx REST API Reference

Languages
Servers
Mock server
https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi
URL:
https://{baseUrl}/pricefx/{partition}

General

Operations

Products

Operations

Product Extensions

Operations

Product Image

Operations

Customers

Operations

Customer Extensions

Operations

Sellers

Operations

Seller Extensions

Operations

Condition Records

Operations

Competition Data

Operations

Imports

Operations

Data Change Requests

Operations

Lookup Tables / Company Parameters

Operations

User Admin

Operations

Authentication

Operations

Admin Tools

Operations

Logics

Operations

Logs

Operations

Custom Forms

Operations

Calculated Field Sets

Operations

Jobs & Tasks

Operations

Data Manager

Operations

Actions

Operations

Action Types

Operations

Price Lists

Operations

Manual Price Lists

Operations

Live Price Grids

Operations

Calculation Grids

Operations

Visual Configuration

Operations

Quotes

Operations

Contracts (Agreements & Promotions)

Operations

Visual Configuration

Operations

Rebate Agreements

Operations

Rebate Calculations

Operations

Rebate Record Group

Operations

Sales Compensations

Operations

Claim Types

Operations

Claims

Operations

Optimization

Operations

Workflow

Operations

Workflow Delegation

Operations

Attachments

To upload a file you need to perform the following actions using endpoints in this category:

  1. Create an Upload Slot
  2. Upload a File
  3. Delete an Upload Slot
Operations

Product Image

Operations

Configuration

Operations

Internationalization

Operations

Metadata

Operations

Clicmanager

Clicmanager (CLIC = "Calculable Line Item Collection") endpoints are used in the REACT version to manipulate Quote/Agreements & Promotions (Contract)/Rebate Agreement/Compensation Plan objects.

Operations

Comments

Operations

Notifications

Operations

Heartbeat

Operations

Key-Value Store

See the Key-Value Database Storage Knowledge Base article for more details.

Operations

Drop a KV Table

Request

Drops (deletes) a table in the Key-Value Database Storage.

Security
basic or X-PriceFx-jwt
Path
tableNamestringrequired

A name of the table you want drop. Only lower case letters, numbers and underscores are allowed. Do not use special characters.

Bodyapplication/json
object
curl -i -X POST \
  -u <username>:<password> \
  'https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/kvservice.droptable/{tableName}' \
  -H 'Content-Type: application/json' \
  -d '{}'

Responses

Table dropped.

Bodyapplication/json
object
Response
application/json
{}

List KV Tables

Request

Retrieves a list of tables in the Key-Value Database.

Security
basic or X-PriceFx-jwt
curl -i -X GET \
  -u <username>:<password> \
  https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/kvservice.listtables

Responses

OK

Bodyapplication/json
responseobject
Response
application/json
{ "response": { "node": "node", "csrfToken": "token", "data": [], "status": 0 } }

Insert Bulk KV Data

Request

Inserts bulk data to the Key-Value Store.
Existing Primary Key combos are overwritten automatically. This is the only command where you explicitly have to specify the automatic “payload” column. While technically you could put any text into that column, other endpoints and Groovy perform JSON conversions (e.g. return a proper map) when you perform key lookups. So inserting a valid JSON into payload is highly recommended!

Security
basic or X-PriceFx-jwt
Path
tableNamestringrequired

A name of the table you want upload data to.

Bodyapplication/json
dataobject
curl -i -X POST \
  -u <username>:<password> \
  'https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/kvservice.loaddata/{tableName}' \
  -H 'Content-Type: application/json' \
  -d '{
    "data": {
      "header": [
        "sku",
        "customer",
        "record",
        "payload"
      ],
      "data": [
        [
          "A1",
          "83-3126689",
          1,
          "{ ... JSON ... }"
        ],
        [
          "A1",
          "45-0245039",
          1,
          "{ ... JSON ... }"
        ],
        [
          "A2",
          "02-0995855",
          1,
          "{ ... JSON ... }"
        ]
      ]
    }
  }'

Responses

A general response that contains data property with a content depending on returned objects (e.g., Product master table fields when calling the /fetch/P endpoint). Can be null.

Bodyapplication/json
responseobject
Response
application/json
{ "response": { "node": "string", "data": null, "status": 0, "startRow": 0, "endRow": 0 } }

Entities

Here you can find all fields of the corresponding entity (represented by the type code).
Use the /metadata.describe endpoint to find out the correct data type of the field that is used in your partition.

otherSchemas

Schemas