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

Get a DM Export File

Request

Retrieves the file created using /datamart.export endpoint. Get the file name via datamart.getactionstatus/{actionUUID} endpoint.

Security
basic or X-PriceFx-jwt
Path
fileNamestringrequired

The name of the file previously created by a datamart.export request. The filename needs to be an exact match - no wildcards allowed, hence only one file at the time can be fetched.

Example: DMDS.Txn_PO_Test_0001_part_00.gz
curl -i -X POST \
  -u <username>:<password> \
  https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/datamart.fetchexportfile/DMDS.Txn_PO_Test_0001_part_00.gz

Responses

OK

Get Action Status

Request

Retrieves the link of the exported file in the result property. Use the /datamart.fetchexportfile/{fileName} to download the file.

Security
basic or X-PriceFx-jwt
Path
actionUUIDstringrequired
curl -i -X POST \
  -u <username>:<password> \
  'https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/datamart.getactionstatus/{actionUUID}'

Responses

OK

Bodyapplication/json
responseobject
Response
application/json
{ "response": { "node": "pricefx-cluster-app-frontend-689c85c8b6-qqmd9", "startRow": 0, "data": [], "endRow": 1, "totalRows": 1, "status": 0 } }

Export Datamart

Request

Exports the specified Datamart source. Typically used in an integration scenario (IM) for a given customer. The request’s body can contain a data block with a regular filter criteria definition (as, for example, used in the JSON API fetch commands), to filter the output rows.

If the Analytics database for the parition is hosted in AWS, the export file(s) will be transferred to the corresponding S3 bucket, ready for retrieval using the datamart.fetchexportfile (Get a DM Export File) endpoint. Otherwise the files are put in the local file system of the node that handles the request:

default path: server/temp/<node>/export/<partition>/

If needed, a different, absolute path can be set using an instance parameter:

datamart.database.export.path

Data is exported in the CSV format, and is always gzip-compressed. Character encoding is always UTF-8. There is no client side encryption.

Security
basic or X-PriceFx-jwt
Path
fcTypedIdOrSourceNamestringrequired

Restricts the export to a specific source, identified by either the 'typedId' or 'sourceName'.

Example: DMDS.SegmentPrices
Query
suffixstring

A suffix appended to the standard output file name: <typeCode>_<sourceUniqueName>_<suffix>.csv.gz

maxRowsstring

The maximum number of returned rows.

Bodyapplication/json
dataobject
curl -i -X POST \
  -u <username>:<password> \
  'https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/datamart.export/DMDS.SegmentPrices?suffix=string&maxRows=string' \
  -H 'Content-Type: application/json' \
  -d '{
    "data": {
      "criteria": [
        {
          "operator": "string",
          "fieldName": "string",
          "value": "string"
        }
      ],
      "operator": "string"
    }
  }'

Responses

OK

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

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