NCR Voyix · Rate Limits

Ncr Rate Limits

The NCR Voyix Business Services Platform does not publish specific numeric per-second / per-minute request-rate limits in its public developer documentation; limits are applied per organization and per service at the platform gateway and may be raised by working with NCR Voyix. The platform documents a correlation header (nep-correlation-id) that is echoed back in responses and propagated across downstream services to aid tracing and throttling diagnostics. Consumers should implement exponential backoff and honor Retry-After on 429 responses. Both production (api.ncr.com) and staging (gateway-staging.ncrcloud.com) are subject to gateway throttling.

Ncr Rate Limits is the machine-readable rate-limit profile for NCR Voyix on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring varies.

Limit state is signalled in the correlationId and retryAfter response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include Rate Limiting, Commerce, and Point of Sale.

2 Limits Exhausted: HTTP 429 Quota: 429 correlationIdretryAfter
Method: generated, dated 2026-06-02.
Written by API Evangelist on 2026-06-02 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingCommercePoint of Sale

Limits

Per-organization gateway throttling (production) account/region/service
varies
not publicly documented; per-organization and per-service limits enforced at the api.ncr.com gateway
Contact NCR Voyix to confirm or raise service-specific limits for production workloads.
Per-organization gateway throttling (staging) account/region/service
varies
sandbox/staging limits apply at gateway-staging.ncrcloud.com
Staging is intended for development and Test Drive trials; do not load-test against it.

Policies

Exponential backoff
On a 429 response, retry with exponential backoff and jitter; honor the Retry-After header when present.
Request correlation
Supply a unique nep-correlation-id header on each request. It is echoed in the response and forwarded to downstream services, enabling end-to-end tracing of throttling and errors.
Scoping
Rate accounting is scoped by organization (nep-organization) and, for site-scoped operations, by enterprise unit (nep-enterprise-unit).
Raise via support
Production service limits are adjustable; engage NCR Voyix support to raise limits for high-volume integrations.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/ncr-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.