Skip to content
Pricefx REST API
/Pricefx API Reference/
/
List Condition Types

The Pricefx Backend API

Pricefx REST API Reference

Download OpenAPI description
pricefx-server_openapi.json
pricefx-server_openapi.yaml
Overview
URL
https://www.pricefx.com
Pricefx
documentation@pricefx.com
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

Add a Condition Type

Request

Creates a Condition Type record in the Compensation Condition Types table.

Security
basic or X-PriceFx-jwt
Bodyapplication/json
dataobject(CompensationConditionType)

The CompensationConditionType object. The type code is COCT.

Defines which logic will be used to calculate particular Compensation Condition Type and what parameters (in attributeX fields) will be available to the logic when it executes.

Whether you use a different logic for various Compensation Condition Types or the same logic, depends on how much different the processes behind the various Compensation Condition Types are.

operationTypestring
curl -i -X POST \
  -u <username>:<password> \
  https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/add/COCT \
  -H 'Content-Type: application/json' \
  -d '{
    "data": {
      "uniqueName": "SingleTargetAmount",
      "label": "Single Target Amount",
      "formulaName": "SC_Compensation",
      "attribute1": "Header Level",
      "attribute3": "Annually",
      "attribute4": "Fixed Amount",
      "attribute5": 2,
      "attribute9": "Annual",
      "attribute11": "Non-Cumulative"
    },
    "operationType": "add"
  }'

Responses

OK

Bodyapplication/json
responseobject(addConditionTypeResponse)
Response
application/json
{
  "response": {
    "node": "node1",
    "data": [ … ],
    "status": 0
  }
}

List Condition Types

Request

Retrieves one or more (based on filter settings) Condition Types from the Compensation Condition Types table.

Security
basic or X-PriceFx-jwt
Bodyapplication/json
endRowinteger
oldValuesobject or null
operationTypestring
startRowinteger
textMatchStylestring
dataobject
curl -i -X POST \
  -u <username>:<password> \
  https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/fetch/COCT \
  -H 'Content-Type: application/json' \
  -d '{
    "endRow": 0,
    "oldValues": {},
    "operationType": "string",
    "startRow": 0,
    "textMatchStyle": "string",
    "data": {
      "_constructor": "string",
      "operator": "string",
      "criteria": [
        {
          "fieldName": "string",
          "operator": "string",
          "value": 0
        }
      ]
    }
  }'

Responses

OK

Bodyapplication/json
responseobject(listConditionTypesResponse)
Response
application/json
{
  "response": {
    "node": "node1",
    "startRow": 0,
    "data": [ … ],
    "endRow": 1,
    "totalRows": 1,
    "status": 0
  }
}

Update a Condition Type

Request

Updates a Condition Type in the Compensation Condition Types table. The version property must be provided within the oldValues.

Security
basic or X-PriceFx-jwt
Bodyapplication/json
dataobjectrequired
data.​uniqueNamestring
data.​labelstring
data.​userGroupEditstring
data.​userGroupViewDetailsstring
data.​typedIdstring
oldValuesobject
operationTypestring
textMatchStylestring
curl -i -X POST \
  -u <username>:<password> \
  https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/update/COCT \
  -H 'Content-Type: application/json' \
  -d '{
    "data": {
      "uniqueName": "test_updated",
      "label": "test - updated",
      "userGroupEdit": "Administrators",
      "userGroupViewDetails": "PricingManagers",
      "typedId": "18.COCT"
    },
    "oldValues": {
      "version": 2,
      "typedId": "18.COCT",
      "uniqueName": "test",
      "label": "test",
      "userGroupEdit": null,
      "userGroupViewDetails": null,
      "formulaName": null,
      "waterfallElement": null,
      "createDate": "2022-06-20T09:46:41",
      "createdBy": 2147490696,
      "lastUpdateDate": "2022-06-21T09:31:35",
      "lastUpdateBy": 2147490696,
      "attribute1": null,
      "attribute2": null,
      "attribute3": null,
      "attribute4": null,
      "attribute5": null,
      "attribute6": null,
      "attribute7": null,
      "attribute8": null,
      "attribute9": null,
      "attribute10": null,
      "attribute11": null,
      "attribute12": null,
      "attribute13": null,
      "attribute14": null,
      "attribute15": null,
      "attribute16": null,
      "attribute17": null,
      "attribute18": null,
      "attribute19": null,
      "attribute20": null,
      "attribute21": null,
      "attribute22": null,
      "attribute23": null,
      "attribute24": null,
      "attribute25": null,
      "attribute26": null,
      "attribute27": null,
      "attribute28": null,
      "attribute29": null,
      "attribute30": null
    },
    "operationType": "update",
    "textMatchStyle": "exact"
  }'

Responses

OK

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

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