Pricefx REST API Reference
The Pricefx Backend API
- Mock serverhttps://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/add/SL
- URL:https://companynode.pricefx.com/pricefx/companypartition/add/SL
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
-u <username>:<password> \
https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/add/SL \
-H 'Content-Type: application/json' \
-d '{
"data": {
"sellerId": "Seller01",
"name": "Acme ltd.",
"reportsTo": "admin",
"userGroupEdit": "Administrators"
},
"operation": "add"
}'{ "response": { "node": "e2e-templates-node", "data": [ … ], "status": 0 } }
Request
Retrieves all sellers based on filter settings.
You can choose fields to be returned in the response by employing the resultFields or valueFields filter:
resultFields: returns key-value pairs as objects. This is the more friendly response compared to valueFields but the server fetches all fields from the database in the backend which might result in a slower performance. See the List Customers' listCustomersResponseExample_resultFields response example.
valueFields: returns just an array of values. Use this option if a better performance is required. See the List Customers' listCustomersResponseExample_valueFields response example.
- Mock serverhttps://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/sellermanager.fetchformulafilteredsellers
- URL:https://companynode.pricefx.com/pricefx/companypartition/sellermanager.fetchformulafilteredsellers
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
-u <username>:<password> \
https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/sellermanager.fetchformulafilteredsellers \
-H 'Content-Type: application/json' \
-d '{
"endRow": 300,
"oldValues": null,
"operationType": "fetch",
"startRow": 0,
"textMatchStyle": "exact",
"data": {
"_constructor": "AdvancedCriteria",
"operator": "and",
"criteria": [
{
"fieldName": "name",
"operator": "equals",
"value": "Acme ltd."
}
]
}
}'{ "response": { "node": "e2e-templates-node", "startRow": 0, "data": [ … ], "endRow": 1, "totalRows": 1, "status": 0 } }
- Mock serverhttps://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/update/SL
- URL:https://companynode.pricefx.com/pricefx/companypartition/update/SL
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
-u <username>:<password> \
https://api.pricefx.com/_mock/openapi/reference/pricefx-server_openapi/update/SL \
-H 'Content-Type: application/json' \
-d '{
"data": {
"sellerId": "Seller0023",
"typedId": "10.SL"
},
"oldValues": {
"version": 4
},
"operationType": "update",
"textMatchStyle": "exact"
}'{ "response": { "node": "e2e-templates-node", "data": [ … ], "status": 0 } }
See the Key-Value Database Storage Knowledge Base article for more details.
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.
Comments