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

Advanced Configuration Options

Operations

Data Manager

Operations

Actions

Operations

Action Types

Operations

Price Lists

Operations

Manual Price Lists

Operations

Live Price Grids

Operations

Submit Products

Request

Submits or approves Live Price Grid (LPG) items. The same endpoint covers both actions: when called on unsubmitted items it performs a submit, and when called with the same payload on items that are already submitted it performs an approval. The Pricefx UI uses this single endpoint for both the Submit and Approve actions, which means repeated or concurrent calls (for example, two users submitting the same change at nearly the same time, or a double-click on Submit) can cause an item to move directly from Unsubmitted to Approved from the first caller's perspective.

In workflows with more than one approval step, each call to accept on a SUBMITTED item advances the item by exactly one step (the workflow's current step) by default. The system can be configured so that one approval automatically triggers the next when the calling user has permission to approve the next step; in that case, a single call in a multi-step workflow can result in the item being fully approved. Otherwise, repeated calls — by the same or different approvers, depending on workflow configuration — progress the item through each step until the final approval completes the workflow.

The endpoint does not distinguish between "step approval" and "final approval" in its API surface; both are the same call, and the workflow engine determines the effect based on the step the item is currently on.


Required PermissionRoles with the Required Permission
PRICEGRID_SUBMITEdit LPG & Add Products (PB_PRICEGRIDEDITOR_ADD_SKU), Edit LPG (PB_PRICEGRIDEDITOR), Administer LPG (PB_PRICEGRIDS)
Security
basic or X-PriceFx-jwt
Path
idstringrequired

The id of the Live Price Grid you want to submit items for. You can retrieve the id of the LPG, for example, by calling the /fetch/PG endpoint.

Bodyapplication/json
dataobjectrequired
data.​idsArray of objectsrequired

Specify typedIds of items you want to accept.

curl -i -X POST \
  -u <username>:<password> \
  'https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/pricegridmanager.accept/{id}' \
  -H 'Content-Type: application/json' \
  -d '{
    "data": {
      "ids": [
        "12.XPGI",
        "13.XPGI",
        "17.XPGI",
        "18.XPGI",
        "19.XPGI"
      ]
    }
  }'

Responses

OK - In case that more than one item is passed in the request, the body will not contain any data ("data":null). For a single item, the new PriceGridItem object is returned.

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

List Live Price Grids

Request

Retrieves all Price Grids based on filter settings.


Filter example:

Returns only Price Grids where status = CANCELLED.

{
   "data":{
      "_constructor":"AdvancedCriteria",
      "operator":"and",
      "criteria":[
         {
            "fieldName":"status",
            "operator":"equals",
            "value":"CANCELLED"
         }
      ]
   }
}

Security
basic or X-PriceFx-jwt
Bodyapplication/json
endRownumber

The number of the end row that defines the end of the result set's returned objects. Use this parameter if you want to implement paging for results.

Default 300
oldValuesany
operationTypestringnon-empty
startRownumber

The number of the first row that defines the start of the result set's returned objects. Use this parameter if you want to implement paging for results.

textMatchStylestringnon-empty
dataobject
curl -i -X POST \
  -u <username>:<password> \
  https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/fetch/PG \
  -H 'Content-Type: application/json' \
  -d '{
    "endRow": 300,
    "oldValues": null,
    "operationType": "fetch",
    "startRow": 0,
    "textMatchStyle": "exact",
    "data": {
      "_constructor": "AdvancedCriteria",
      "operator": "and",
      "criteria": [
        {
          "fieldName": "status",
          "operator": "equals",
          "value": "READY"
        }
      ]
    }
  }'

Responses

OK

Bodyapplication/json
responseobject
Response
application/json
{ "response": { "status": 0, "startRow": 0, "node": "string", "csrfToken": "string", "data": [ … ], "endRow": 300 } }

Get a Live Price Grid

Request

Retrieves details of the specified Live Price Grid.

Security
basic or X-PriceFx-jwt
Path
idstringrequired

The id of the Live Price Grid you want to retrieve details for. You can retrieve the id of the LPG, for example, by calling the /fetch/PG endpoint.

curl -i -X POST \
  -u <username>:<password> \
  'https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/fetch/PG/{id}'

Responses

OK

Bodyapplication/json
responseobjectrequired
response.​nodestringnon-emptyrequired
response.​csrfTokenstringnon-emptyrequired
response.​dataArray of objectsnon-emptyuniquerequired
response.​data[].​versionnumber
response.​data[].​typedIdstringnon-empty
response.​data[].​labelstringnon-empty
response.​data[].​calculationMessagesstringnon-empty
response.​data[].​numberOfItemsnumber
response.​data[].​keepManualOverridesboolean
response.​data[].​writeOnlyChangedItemsboolean
response.​data[].​configurationstringnon-empty
response.​data[].​numberOfApprovedItemsnumber
response.​data[].​numberOfOpenItemsnumber
response.​data[].​numberOfDeniedItemsnumber
response.​data[].​numberOfSubmittedItemsnumber
response.​data[].​numberOfAutoApprovedItemsnumber
response.​data[].​priceGridTypestringnon-empty
response.​data[].​createdByNamestringnon-empty
response.​data[].​lastUpdateByNamestringnon-empty
response.​data[].​updateDatestringnon-empty
response.​data[].​updatedBynumber
response.​data[].​createDatestringnon-empty
response.​data[].​createdBynumber
response.​data[].​lastUpdateDatestringnon-empty
response.​data[].​lastUpdateBynumber
response.​data[].​statusstringnon-empty
response.​data[].​calculationStartDatestringnon-empty
response.​data[].​calculationDatestringnon-empty
response.​data[].​partialCalculationDatestringnon-empty
response.​data[].​idnumber
response.​statusnumberrequired
Response
application/json
{ "response": { "node": "string", "csrfToken": "string", "data": [ … ], "status": 0 } }

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

Operations

Product Image

Operations

Configuration

Operations

Internationalization

Operations

Metadata

Operations

MCP

Operations

Clicmanager

Operations

Comments

Operations

Notifications

Operations

Heartbeat

Operations

Key-Value Store

Operations

Entities

otherSchemas

Schemas