InfiPlex API Reference

The InfiPlex REST API connects your ERP, WMS, or custom application directly to your InfiPlex account. Pull orders from every connected marketplace, send tracking back, update inventory and pricing across all of your sales channels, and manage products, warehouses, and settings, all through one integration.

API calls run through InfiPlex exactly like actions taken in the OMS. Tracking you post is forwarded to the order's marketplace automatically, and inventory and price updates are queued to every connected channel with that sync enabled.

Getting Started

1. API access is included with the Growth and Enterprise packages. See InfiPlex pricing.
2. Contact InfiPlex Support for your API key and your API URL.
3. In this collection, every request uses the {{api_url}} variable. Set it to your API URL in your Postman environment.
4. Send every request with your API key in the Authorization header, as shown below.

Authentication

The InfiPlex API uses Bearer token authentication. Send your API key in the Authorization header of every request:

Authorization: Bearer YOUR_API_KEY

Example request:

curl "YOUR_API_URL/shop/order/search?limit=10" -H "Authorization: Bearer YOUR_API_KEY"

Send the key in the header only, never in the URL.

Permissions

Each API key has separate read and write permissions for each area: Orders, Inventory, Prices, Products, PIM, Warehouses, Settings, Passthrough, and Amazon Today. A key only reaches the areas it has been granted, and a read-only key cannot change data. Ask InfiPlex Support to adjust the permissions on your key.

Requests and Responses

• OMS endpoints live under {{api_url}}/shop/.
• Request bodies and responses are JSON. Send Content-Type: application/json on POST and PUT requests.
• Date filters use the format 2018-01-01 10:10:10 AM.
• Order endpoints take the InfiPlex order ID (orderid), not the marketplace order number. Use Order Search to find an order by its marketplace number.
• The bulk inventory, bin location, and product create endpoints take a JSON array as the body root, one object per item.

Syncing Orders

The standard integration loop:

1. Pull orders: Order Search with date_created_greater_equal_than set to your last check, so you only pull new orders. Check for duplicates before inserting.
2. Send tracking: Order Tracking Create. InfiPlex forwards the tracking to the order's marketplace automatically.
3. Send inventory: Inventory Set Bulk updates levels across your SKUs in one call.

Order PII (the ship-to address) is retained only for a limited time after the order is placed, per Amazon's data security requirements. Pull and store the order data you need promptly.

Pagination

Search endpoints return results in pages:

• limit: results per page. Most search endpoints cap this at 100.
• limit_start: number of results to skip. Use 0 for the first page, 100 for the second page at limit=100, and so on.
• Keep paging until a page returns fewer results than your limit.
• just_count=1 returns only the number of matching records, with no results.

Error Codes

The InfiPlex API returns standard HTTP status codes. 2xx means success, 4xx means the request needs to be corrected, and 5xx means retry.

Support

API support is included with every InfiPlex package, and our team answers developer questions on the API directly. Contact InfiPlex.

Related guides:

• InfiPlex OMS API Overview
• InfiPlex Data Bridge: One REST API, Every Sales Channel
• Multichannel Inventory Sync
• Order Automation Overview
• Warehouse Management Set-up
• Manual Order Import