API Rate Limits for Manhattan Active Solutions

Warehouse, Transport Management & Omni-channel Commerce

Manhattan Active APIs are designed to support secure, reliable integrations while helping maintain consistent platform performance across all customers.

These APIs use a REST-based model and exchange JSON payloads.

Why API tier limits exist

API rate limits are an important part of service protection.

They help promote stable platform performance, support predictable operations, and enable reliable service delivery across the Manhattan Active environment.

What does this mean for customers?

If you integrate external systems with Manhattan Active Warehouse (WM), Transportation Management (TM), or Omnichannel Commerce, your API usage is observed by your subscription-based entitlement.

In practice, this means:

  • Your solution subscription determines your starting API entitlement.
  • Your API traffic should operate within the entitled usage limits.
  • Large spikes, aggressive polling, or inefficient integration patterns should be avoided through good solution design (to stay within your entitlement).
  • If you anticipate sustained higher usage, it is best to plan for that early and consider additional API volume packs to increase your entitlement.

How is the API rate measured?

API rate is measured on an hourly basis for production environments at the tenant level.

This includes total API traffic generated in the production environment, including:

  • API traffic across all integrations
  • API calls generated through operational user workflows
  • API activity generated by Manhattan to operate and support the application

Tier limits by solution

API entitlement is determined by the limits associated with your subscription.

Volume add-on packs are available for all customers across Active Warehouse, Active Transport Management and Active Omni-channel Commerce to provide additional hourly capacity.

Active Warehouse

  • 500 API calls per user per hour
  • Example: If your warehouse management subscription includes 100 users, your hourly API entitlement is: 500 × 100 = 50,000 API calls per hour

Active Omni-channel Commerce

The MAO API rate limit is modular and calculated per 1,000 orders/hour, depending on the subscribed modules:

  • Baseline Cap: 25 API calls/hour per 1,000 orders
  • Contact Center: Adds 30 API calls/hour per 1,000 orders
  • Store Fulfillment: Adds 30 API calls/hour per 1,000 orders
  • POS (Point of Sale): Upgrades the baseline from 25 to 65 API calls/hour per 1,000 orders
  • Note: For subscribers of Interactive Inventory/Promising, API calls generated by these modules do not count toward your calculated API rate limit.

Active Transport Management

  • 80 API calls/hour per $1M FUM
  • Example: If you’ve subscribed for $5M FUM, then your entitlement is 80 × 5 = 400 API calls per hour.

If usage exceeds the entitlement

If API usage goes above the allowed limit, integrations should be designed to respond gracefully.

This includes spacing requests appropriately, retrying responsibly, and avoiding burst traffic patterns.

When sustained usage is expected to exceed the current entitlement, additional API packs can be added to support higher volumes.

To help customers get the best performance and reliability from Manhattan Active APIs, we recommend the following practices:

  • Use a dedicated credential for each integration.
  • Prefer event-driven integration patterns over frequent polling.
  • Cache and reuse responses, where appropriate.
  • Retry only transient failures with capped exponential backoff and jitter.
  • Use idempotency for write operations so retries can be handled safely.
  • Queue and smooth bursts instead of sending traffic in spikes.
  • Monitor usage regularly and review peak-hour traffic before go-live.
  • Separate real-time traffic from bulk traffic and use asynchronous patterns for bulk exchange where possible.
  • Engage early when planning for new channels, migrations, seasonal peaks, or other expected growth.
  • Add API packs when sustained higher usage is anticipated.

These practices align with Manhattan guidance and established SaaS integration patterns.

Monitoring and support

Customers are encouraged to review their API utilization with Manhattan to ensure alignment with their entitled limits.

Manhattan Cloud Operations continuously monitors API usage and will discuss with the customer in case of consistent overage above the entitlement.

If you are planning a new high-volume integration or expect sustained usage above your current entitlement, please contact Manhattan Support early.

Early engagement helps ensure the integration design and projected traffic can be reviewed in advance and that any required entitlement adjustments can be addressed before go-live.