Annex Cloud · Rate Limits

Annex Cloud Rate Limits

Annex Cloud does not publish fixed numeric rate limits for its Loyalty Experience Platform APIs. Because access is enterprise and tenant-provisioned, throughput and any per-account throttles are governed by the customer's contract and platform configuration rather than by publicly documented per-minute request caps. Bulk endpoints (for example POST /bulkpostusers, POST /bulkproducts) exist specifically to move large volumes efficiently, which implies per-request batching is the intended path for high-volume work. Verify any applicable limits with your Customer Success Manager.

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

It captures 2 rate-limit definitions, measuring requests and records.

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 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Loyalty, Customer Retention, Rate Limiting, Quotas, and Enterprise.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-10.
Written by API Evangelist on 2026-07-10 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
LoyaltyCustomer RetentionRate LimitingQuotasEnterprise

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented; governed by the enterprise contract and tenant configuration.
Bulk Operations request
records
batch-based
Bulk endpoints (bulkpostusers, bulkpatchusers, bulkproducts, bulkpatchproducts) batch many records per request for high-volume workloads.

Policies

Contract-Governed
Throughput and any throttling are set by the customer's enterprise agreement and tenant provisioning, not by public per-endpoint caps.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.

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/annex-cloud-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.