Microsoft Dynamics NAV · Rate Limits

Navision Rate Limits

Microsoft Dynamics NAV's modern successor — Dynamics 365 Business Central — publishes operational limits per environment and per user for OData v4, REST API, and SOAP endpoints. Production environments allow 600 requests/min/environment (legacy) and 6,000 requests per 5-minute sliding window per user. Sandbox environments are capped at 300 requests/min. Throttling returns HTTP 429 with retry guidance; 504/503 may indicate queueing or timeout.

Navision Rate Limits is the machine-readable rate-limit profile for Microsoft Dynamics NAV on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 20 rate-limit definitions, measuring requests_per_5_minutes, requests_per_minute, concurrent_requests, queued_requests, and entities_per_response.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, payloadTooLarge, requestTimeout, and serviceUnavailable.

Tagged areas include Rate Limiting, ERP, Microsoft, Navision, and Dynamics NAV.

20 Limits Throttle: 429
Rate LimitingERPMicrosoftNavisionDynamics NAV

Limits

OData speed (rate) — per user user
requests_per_5_minutes · minute
6000
5-minute sliding window. Distribute load across multiple users / service principals.
OData speed (rate) — production (legacy per-environment) environment
requests_per_minute · minute
600
Legacy per-environment limit superseded by per-user limits in late 2023.
OData speed (rate) — sandbox (legacy per-environment) environment
requests_per_minute · minute
300
OData max concurrent requests — per user user
concurrent_requests
5
OData max connections — per user user
concurrent_requests
100
Includes processed and queued requests; exceeds returns 429.
OData max request queue size — per user user
queued_requests
95
OData max page size environment
entities_per_response
20000
Returns 413 Request Entity Too Large.
OData max body size environment
mb_per_request
350
OData max batch size environment
operations_per_batch
100
OData operation timeout environment
minutes
8
Returns 408 Request Timeout.
SOAP speed (rate) — per user user
requests_per_5_minutes · minute
6000
SOAP endpoints scheduled for deprecation; prefer OData / REST API.
SOAP max concurrent requests environment
concurrent_requests
5
SOAP max connections environment
concurrent_requests
100
SOAP max message size environment
kb_per_request
65536
Webhook subscriptions environment
subscriptions
200
Max file upload size environment
mb_per_file
350
Companies per environment environment
companies
300
Background sessions concurrency environment
concurrent_sessions
10
Background sessions queue length environment
queued_sessions
100
Scheduled tasks (per user) user
concurrent_tasks
5

Policies

429 throttling and retry
Exceeding rate or queue limits returns HTTP 429 Too Many Requests. Implement retry logic with exponential backoff; honor Retry-After when present.
503 queue timeout
When the concurrent-request queue is saturated, requests wait up to 8 minutes; if not processed they return 503 Service Temporarily Unavailable.
Per-user fan-out
Per-user limits are strict. Spread workload across multiple users or service principals using round-robin to scale beyond a single user's quota.
SOAP deprecation
SOAP endpoints have reduced throughput targets and are slated for deprecation; migrate to REST API or OData v4.
Sandbox vs production
Sandbox environments have lower legacy per-environment caps (300 vs 600 rpm). Do not load-test in sandbox.

Sources