Nectar · Rate Limits

Nectar Hr Rate Limits

Nectar's Open API documents a concurrency limit rather than a published per-minute request quota - a maximum of 50 concurrent calls per account. Several endpoints also impose payload/pagination caps: the user upsert endpoint (PUT /v1/users) accepts up to 50 users per request, list and feed endpoints are cursor-paginated (users default/limit-bounded, custom awards default 25 per page), and the financial redemptions report caps its date span at one year. A single API key is issued per account, with selectable scopes and an optional expiration.

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

It captures 6 rate-limit definitions, measuring concurrent-requests, requests, users, items, and days.

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

Tagged areas include Employee Recognition, HR, Rate Limiting, and Quotas.

6 Limits Throttle: 429
Employee RecognitionHRRate LimitingQuotas

Limits

Concurrent Calls account
concurrent-requests
50
Documented maximum of 50 concurrent API calls per account.
Request Rate account
requests
not published
No fixed numeric per-minute or per-day request-rate limit is documented.
User Upsert Batch request
users
50
PUT /v1/users upserts up to 50 users per request (matched on nectar_id, email, or employee_id).
Custom Awards Page Size request
items
25 (default)
GET /v1/custom-awards returns a page defaulting to 25 items.
Redemptions Report Span request
days
365
GET /v1/analytics/financial/redemptions date range cannot span more than one year.
API Keys account
keys
1
One scoped API key per account, generated in Settings > Integrations, with optional expiration.

Policies

Authentication
Every endpoint requires an Authorization: Bearer (JWT) header; access is a plan-gated add-on enabled by Nectar.
Cursor Pagination
List and feed endpoints use cursor-based pagination; follow the returned cursor rather than issuing large single requests.
Backoff Strategy
Clients should stay under the 50-concurrent-call ceiling and implement exponential backoff with jitter, honoring Retry-After on 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/nectar-hr-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.