Integration Requirements - 3PLCentral WMS

Last updated: September 29, 2026

Basic Requirements

When integrating your 3PLCentral instance, Techdinamics will require the following information:

  • REST API keys (provided in a text file by the 3PLCentral implementation team according to the permissions below)
  • Customer ID(s) (numeric value)
  • Facility ID(s) (numeric value)
  • Single SKU mapping list, if needed
  • Single Carrier mapping list, if needed


When requesting the keys from the 3PLCentral implementation team, please make sure the following permissions are assigned at the minimum:


Item details Rels:

GET: customers/{customerId}/items/{itemId}

GET: customers/{customerId}/items?sku=={sku}

 

Receiver rels:

GET: inventory/receivers/{id}

GET/POST: inventory/receivers

GET: rels/reportdefs/ssrsrun

 

Order Rels:

GET/PUT: orders/{orderId}

GET/PUT: orders

GET: orders/{orderId}/packages

GET/PUT: orders/{orderId}/packages/{packageId}

POST: orders/{orderId}/confirmer

 

Purchase order rels:

GET/PUT: inventory/pos/{id}

GET/POST: inventory/pos


Carrier mapping rels:

GET: properties/carriers

GET: properties/carriers/{name}


Optional - required only for IntegratedBilling connections

GET/PUT customers/itemizedchargeslist


Known Issues

Inventory Advice

Due to 3PLCentral's internal workings most inventory methods do not support items without any stock. 
  • Workaround 1: use a method with inbuilt Items request. Currently does not support Lot Details.
  • Workaround 2: maintain a SKU table within Techdinamics' system and use that to identify missing SKUs.


Alias Items

Inbuilt aliases are not supported in most integrations due to irreversable item breakdown. 
  • Workaround: use Techdinamics supplied alias solution.