REST and SOAP APIs
Price System Core provides calculated-price endpoints. Optional API packages add CRUD routes for the stored records owned by Customer Price, Price Lists, Category Price and Product-Customer Matrix.
Magento exposes the same service contracts through its normal REST and SOAP layers.
Calculated-price routes
| Context | One SKU | Several SKUs |
|---|---|---|
| Integration or authorized admin | POST /V1/pricesystem/get-final-price |
POST /V1/pricesystem/get-multi-price |
| Signed-in customer | POST /V1/pricesystem/me/get-final-price |
POST /V1/pricesystem/me/get-multi-price |
| Current storefront context | POST /V1/pricesystem/context/get-final-price |
POST /V1/pricesystem/context/get-multi-price |
REST requests normally use /rest/V1/... or /rest/{storeCode}/V1/....
The me routes require a customer token and derive the customer from that token. The context routes use the current signed-in customer or the NOT LOGGED IN group. Do not send an arbitrary customer ID to either of those contexts.
Record APIs
Install only the package for the product an integration must manage:
mageb2b/pricesystem-customerprice-apimageb2b/pricesystem-pricelist-apimageb2b/pricesystem-categoryprice-apimageb2b/pricesystem-productcustomermatrix-api
Each product guide lists its exact resources and routes. Use a Magento integration with only the ACL resources it needs rather than an administrator token embedded in application code.
After a write
Successful repository writes invalidate relevant Price System calculations. For a bulk integration, still verify one affected customer and SKU after the batch and monitor failed API responses before treating the synchronization as complete.