Neon One · Rate Limits

Neonone Rate Limits

Neon CRM API v2 does not rate-limit on requests-per-unit-of-time. Instead it caps the number of simultaneous (concurrent, in-flight) requests permitted per endpoint, per Neon CRM organization instance, described in the docs as "rate limits in terms of number of requests per thread pool." Nearly every endpoint allows up to 5 simultaneous requests; the four search endpoints (POST /accounts/search, POST /donations/search, POST /events/search, POST /orders/search) are limited to 1 simultaneous request each because search queries are the most resource-intensive operation in the API. Limits are independent per endpoint and per organization - concurrent calls to one endpoint do not count against a different endpoint or a different Neon CRM system.

Neonone Rate Limits is the machine-readable rate-limit profile for Neon One on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring simultaneous requests and requests.

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

Tagged areas include Nonprofit, CRM, Fundraising, Rate Limiting, and Quotas.

3 Limits Throttle: 429
NonprofitCRMFundraisingRate LimitingQuotas

Limits

Standard Endpoint Concurrency endpoint
simultaneous requests
5
Default concurrency cap applied per endpoint per organization instance for the large majority of API v2 endpoints (accounts, addresses, pledges, recurring donations, campaigns, donations, events, event registrations, memberships, custom objects, orders, store, volunteers, webhooks, and properties/reference lookups).
Search Endpoint Concurrency endpoint
simultaneous requests
1
Applies specifically to POST /accounts/search, POST /donations/search, POST /events/search, and POST /orders/search - the most computationally expensive requests in the API.
Per-Organization Isolation account
requests
independent per instance
Every Neon CRM organization (instance) has independent rate limits; load on one organization's endpoints does not affect another organization.

Policies

Thread Pool Model
Limits are expressed as concurrent in-flight requests per endpoint rather than a rolling request-per-second/minute window.
Backoff Guidance
Neon recommends sleep functions or a managed request queue in client integrations that need to issue many simultaneous requests, to avoid 429 Too Many Requests 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/neonone-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 email required.

GitHub Google LinkedIn

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