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

Insert Bulk Data From a File (async)

Request

Creates a JST job (the LOADDATA_FILE type) for inserting multiple records to the Master Data table from a CSV file.

You can get the status of the job by calling the admin.fetchjst/{jstId} endpoint. The jstId can be found in the response of the /loaddata.file/{TypeCode}/async endpoint.
Allows parallel loaddata calls. You can also view the job in Administration > Logs > Jobs & Tasks.

The /loaddata operation is a very efficient and quick way to insert bulk data to the Master Data table. The main advantage is its greater speed when loading thousands of records (compared to e.g. /integrate).

If used in a Groovy logic, it is recommended to use the api.addOrUpdate() method instead of this loaddata endpoint within the boundCall().
For more details see the Avoid api.boundCall article.

Please note If no joinFields are provided in the request, then this operation will insert entire records. It means that in this case (without joinFields) with /loaddata.file it is not possible to update just some fields (for this use the /integrate endpoint instead). The source data must always contain the entire row’s content.

Security
basic or X-PriceFx-jwt
Path
TypeCodestringrequired

Enter the type code of the entity you want to insert a data to. See the list of Type Codes in the Pricefx Knowledge Base article.

Enum"C""CDESC""CX""JLTV""LTV""MLTV""P""PBOME""PCOMP""PDESC"
Example: PX
Query
namestring

The name of the table you want to upload a file to.

Bodymultipart/form-data
fileNamestring(binary)required

Provide a file in the CSV format. The file must also contain the name column with the name(s) of the table (PX, CX, SX) you are inserting the records to.

joinFieldsstring

Specify fields that make up a Business key.

curl -i -X POST \
  -u <username>:<password> \
  'https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/loaddata.file/PX/async?name=string' \
  -H 'Content-Type: multipart/form-data' \
  -F fileName=string \
  -F joinFields=string

Responses

OK

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

Upsert an Object

Request

Upserts an object (the object type must be specified by Type Code in the path).

To add a new object that does not exist, specify the sku parameter in the request.

To update an existing object, specify the sku or typedId parameter of the existing object. The /integrate method performs a partial update – it does not delete field values that have not been specified in the update request.

Please note This method is intended to be used with one or two objects and it allows you to update particular fields. The request will overwrite the existing data of the record being updated, regardless of other changes. To insert more objects in bulk, please use the /loaddata/{TypeCode} endpoint.

This operation is particularly useful if the caller does not (and should not) know about typed IDs and other internal data fields, i.e. typically in an integration scenario.

The only mandatory pre-requisite for this operation is that the object's defined business key fields (vary per object type) are present in every request. No typed ID or version fields are required. This also means that no version checking is performed, thus the request will overwrite existing data of that record, regardless of other changes.

Information You can upsert multiple records using one request. To do so, add multiple data objects into your JSON. See the example below.

[
  {
    "data": {
      "sku": "111111",
      "typedId": "2147501227.P",
      "label": "The New Label",
      "unitOfMeasure": "EA",
      "currency": "USD",
      "formulaName": "priceLogic2",
      "attribute1": "1",
      "attribute2": "2",
      "userGroupEdit": "Administrators",
      "userGroupViewDetails": "PricingManagers"
    }
  },
  {
    "data": {
      "sku": "222222",
      "label": "The New Label 2",
      "unitOfMeasure": "EA",
      "currency": "EUR",
      "formulaName": "priceLogic2",
      "attribute1": "1",
      "attribute2": "2",
      "userGroupEdit": "Administrators",
      "userGroupViewDetails": "PricingManagers"
    }
  }
]
Security
basic or X-PriceFx-jwt
Path
TypeCodestringrequired

Enter the Type code of the entity you want to insert a data to. See the list of Type codes in the Pricefx Knowledge Base article.

Enum"ACTT""AP""APIK""BD""BPT""BR""C""CA""CAM""CDESC"
Example: P
Bodyapplication/json

The /integrate/P endpoint (Upsert a Product) is used in our example.

Information: Field names (columns) sent in your request might be different from our sample request schema. Custom fields (attribute1..attribute30) can be retrieved using the /fetch/<entity>AM (AttributeMeta) endpoint, for example, use /fetch/RBTAM to retrieve Rebate Type attribute fields.

dataobjectrequired

Specify field names and values you want to insert or update.

data.​skustringnon-emptyrequired
data.​typedIdstringnon-empty
data.​labelstringnon-empty
data.​unitOfMeasurestringnon-empty
data.​currencystringnon-empty
data.​formulaNamestringnon-empty
data.​attribute1stringnon-empty
data.​attribute2stringnon-empty
data.​userGroupEditstringnon-empty
data.​userGroupViewDetailsstringnon-empty
curl -i -X POST \
  -u <username>:<password> \
  https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/integrate/P \
  -H 'Content-Type: application/json' \
  -d '{
    "data": {
      "sku": "111111",
      "typedId": "2147501227.P",
      "label": "The New Label",
      "unitOfMeasure": "EA",
      "currency": "USD",
      "formulaName": "priceLogic2",
      "attribute1": "1",
      "attribute2": "2",
      "userGroupEdit": "Administrators",
      "userGroupViewDetails": "PricingManagers"
    }
  }'

Responses

Returns full record details.

Bodyapplication/json
responseobject
Any of:
Response
application/json
{ "response": { "node": "node", "startRow": 0, "data": [], "endRow": 8, "totalRows": 8, "status": 0 } }

Upsert an Object (and return old data)

Request

Upserts an object (the object type must be specified by Type Code in the path) and returns record details of the previous version. It allows you to check changes in the record.

To add a new object that does not exist, specify the sku parameter in the request.

To update an existing object, specify the sku or typedId parameter of the existing object. The /integrate method performs a partial update – it does not delete values from fields that have not been specified in the update request.


Please note: This method is intended to be used with one or two objects and it allows you to update particular fields. The request will overwrite the existing data of the record being updated, regardless of other changes. To insert more objects in bulk please use the /loaddata/{TypeCode} endpoint.


This operation is particularly useful if the caller does not (and should not) know about typed IDs and other internal data fields, i.e. typically in an integration scenario.

The only mandatory pre-requisite for this operation is that the object's defined business key fields (vary per object type) are present in every request. No typed ID or version fields are required. This also means that no version checking is performed, thus the request will overwrite existing data of that record, regardless of other changes.

Information: You can upsert multiple records using one request. To do so, add multiple data objects into your JSON. See the example below.

[
  {
    "data": {
      "sku": "111111",
      "typedId": "2147501227.P",
      "label": "The New Label",
      "unitOfMeasure": "EA",
      "currency": "USD",
      "formulaName": "priceLogic2",
      "attribute1": "1",
      "attribute2": "2",
      "userGroupEdit": "Administrators",
      "userGroupViewDetails": "PricingManagers"
    }
  },
  {
    "data": {
      "sku": "222222",
      "label": "The New Label 2",
      "unitOfMeasure": "EA",
      "currency": "EUR",
      "formulaName": "priceLogic2",
      "attribute1": "1",
      "attribute2": "2",
      "userGroupEdit": "Administrators",
      "userGroupViewDetails": "PricingManagers"
    }
  }
]

Security
basic or X-PriceFx-jwt
Path
TypeCodestring(TypeCodeEnum)required

Specify the type code for the entity you want to work with. See the list of Type Codes in the Pricefx Knowledge Base article.'

Enum"ACTT""AP""APIK""BD""BPT""BR""C""CA""CAM""CDESC"
Example: P
Bodyapplication/json

The /integrate/P/returnolddata endpoint (upserts a product) is used in our example.

Please note: Field names (columns) sent in your request might be different from our sample request schema. Custom fields (attribute1..attribute30) can be retrieved using the /fetch/PAM endpoint.

dataobjectrequired

Specify field names and values you want to insert or update.

data.​skustringnon-emptyrequired
data.​labelstringnon-empty
data.​unitOfMeasurestringnon-empty
data.​currencystringnon-empty
data.​formulaNamestringnon-empty
data.​attribute1stringnon-empty
data.​attribute2stringnon-empty
data.​userGroupEditstringnon-empty
data.​userGroupViewDetailsstringnon-empty
curl -i -X POST \
  -u <username>:<password> \
  https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/integrate/P/returnolddata \
  -H 'Content-Type: application/json' \
  -d '{
    "data": {
      "sku": "111111",
      "typedId": "2147501227.P",
      "label": "The New Label",
      "unitOfMeasure": "EA",
      "currency": "USD",
      "formulaName": "priceLogic2",
      "attribute1": "1",
      "attribute2": "2",
      "userGroupEdit": "Administrators",
      "userGroupViewDetails": "PricingManagers"
    }
  }'

Responses

OK

Bodyapplication/json
responseobjectrequired
response.​nodestringnon-emptyrequired
response.​oldDataobjectrequired
response.​oldData.​versionnumberrequired
response.​oldData.​typedIdstringnon-emptyrequired
response.​oldData.​skustringnon-emptyrequired
response.​oldData.​labelstringnon-emptyrequired
response.​oldData.​unitOfMeasurestringnon-emptyrequired
response.​oldData.​userGroupEditstringnon-emptyrequired
response.​oldData.​userGroupViewDetailsstringnon-emptyrequired
response.​oldData.​currencystringnon-emptyrequired
response.​oldData.​formulaNamestringnon-emptyrequired
response.​oldData.​createDatestringnon-emptyrequired
response.​oldData.​createdBynumberrequired
response.​oldData.​lastUpdateDatestringnon-emptyrequired
response.​oldData.​lastUpdateBynumberrequired
response.​oldData.​attribute1stringnon-emptyrequired
response.​oldData.​attribute2stringnon-emptyrequired
response.​csrfTokenstringnon-emptyrequired
response.​dataArray of objectsnon-emptyuniquerequired
response.​data[].​versionnumberrequired
response.​data[].​typedIdstringnon-emptyrequired
response.​data[].​skustringnon-emptyrequired
response.​data[].​labelstringnon-emptyrequired
response.​data[].​unitOfMeasurestringnon-emptyrequired
response.​data[].​userGroupEditstringnon-emptyrequired
response.​data[].​userGroupViewDetailsstringnon-emptyrequired
response.​data[].​currencystringnon-emptyrequired
response.​data[].​formulaNamestringnon-emptyrequired
response.​data[].​imageany
response.​data[].​createDatestringnon-emptyrequired
response.​data[].​createdBynumberrequired
response.​data[].​lastUpdateDatestringnon-emptyrequired
response.​data[].​lastUpdateBynumberrequired
response.​data[].​attribute1stringnon-emptyrequired
response.​data[].​attribute2stringnon-emptyrequired
response.​data[].​attribute3any
response.​data[].​attribute4any
response.​data[].​attribute5any
response.​data[].​attribute6any
response.​data[].​attribute7any
response.​data[].​attribute8any
response.​data[].​attribute9any
response.​data[].​attribute10any
response.​data[].​attribute11any
response.​data[].​attribute12any
response.​data[].​attribute13any
response.​data[].​attribute14any
response.​data[].​attribute15any
response.​data[].​attribute16any
response.​data[].​attribute17any
response.​data[].​attribute18any
response.​data[].​attribute19any
response.​data[].​attribute20any
response.​data[].​attribute21any
response.​data[].​attribute22any
response.​data[].​attribute23any
response.​data[].​attribute24any
response.​data[].​attribute25any
response.​data[].​attribute26any
response.​data[].​attribute27any
response.​data[].​attribute28any
response.​data[].​attribute29any
response.​data[].​attribute30any
response.​statusnumberrequired
Response
application/json
{ "response": { "node": "<node>", "oldData": {}, "csrfToken": "<token>", "data": [], "status": 0 } }

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

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