YourMembership · Rate Limits

Yourmembership Rate Limits

YourMembership does not publish fixed numeric rate limits for its developer APIs in public documentation. The REST API (ws.yourmembership.com) is license-gated - its Swagger UI and metadata document return HTTP 403 to anonymous callers - so any per-account or per-endpoint request caps are only visible to licensed customers/partners. The legacy XML API historically applied session-based throttling and expected reasonable, batched polling for exports rather than high-frequency calls. The separate YMCareers REST API (api.careerwebsite.com/v1) authenticates with a short-lived API_ACCESS_TOKEN (15-minute expiry) that must be refreshed, or a non-expiring X-API-KEY; token lifetime is the primary documented throttling-adjacent constraint.

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

It captures 4 rate-limit definitions, measuring requests, calls, minutes, and records.

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

Tagged areas include Membership Management, Association Management, AMS, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Membership ManagementAssociation ManagementAMSRate LimitingQuotas

Limits

REST API Requests account
requests
not published
License-gated REST API; numeric request caps are not documented publicly.
XML API Sessions session
calls
not published
Legacy XML API is session-based; batch exports and avoid high-frequency polling.
YMCareers Access Token Lifetime token
minutes
15 (token expiry)
API_ACCESS_TOKEN expires after 15 minutes and must be refreshed via the token endpoint; X-API-KEY does not expire.
Export Volume account
records
batch-oriented
Member/transaction/donation exports are intended to be pulled in batches (deltas by modified date) rather than repeatedly in full.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Incremental Sync
Use modified-since / delta queries and pagination for member and transaction data instead of full re-pulls.
Token Refresh
For YMCareers, refresh the 15-minute API_ACCESS_TOKEN proactively, or use a non-expiring X-API-KEY for server-to-server integrations.

Sources