Introduction
Overview
The ShipMonk API enables developers to build custom integrations between ShipMonk and third-party software.
Date and Time
All date and time values follow the ISO 8601 format.
Example: 2022-05-01T11:43:16-04:00
Warehouses
Some API operations allow or require specifying a warehouse for shipments or receivings. Below is the list of ShipMonk warehouse identifiers.
Note: When creating orders, we recommend omitting the warehouse field. ShipMonk automatically routes orders to the optimal warehouse based on inventory availability and shipping cost.
| Warehouse | Identifier |
|---|---|
| California | CA1 |
| Czechia | CZ1 |
| Florida | FL1 |
| Kentucky | KY1 |
| Mexico | MX1 |
| Nevada | NV1 |
| Nevada 3 | NV3 |
| Pennsylvania | PA1 |
| Pennsylvania 2 | PA2 |
| Texas | TX1 |
| Texas Bonded | TX8 |
| Toronto | TO1 |
| United Kingdom | UK1 |
Deprecated warehouses
New orders cannot be routed to these warehouses. Identifiers are retained for historical data and existing references.
| Warehouse | Identifier |
|---|---|
| Bay Shore (Deposco) | NY7 |
| California (Deposco) | CA7 |
| Kentucky (Deposco) | KY7 |
| Nevada 2 | NV2 |
| Nevada (Deposco) | NV7 |
| New Jersey | NJ1 |
| New Jersey (Deposco) | NJ7 |
| Toronto (Deposco) | TO7 |
Rate Limiting
The ShipMonk API is optimized for real-time operations and high-volume usage. While rate limiting is rare under normal conditions, ShipMonk reserves the right to enforce limits when necessary. Client applications should be designed to handle standard HTTP rate limiting responses gracefully.
Sandbox Environment Maintenance
ShipMonk aims to keep the Sandbox environment available at all times. However, periodic maintenance may cause brief downtime between 00:00 - 06:00 EST, typically lasting no longer than 30 minutes. Any extended maintenance windows will be announced in advance.
Updated 6 days ago