MemberClicks · Rate Limits

Memberclicks Rate Limits

MemberClicks does not publish fixed numeric rate limits for the MC Professional API in its public developer documentation. The API is a per-organization, OAuth 2.0-protected REST interface, and access is tenant-scoped by client credentials rather than by a documented per-minute request cap. The one quantitative paging constraint that is documented is on list endpoints: pageSize defaults to 10 and is capped at a maximum of 100 records per page (with pageNumber defaulting to 1). Integrations should page through large result sets and implement backoff on error responses.

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

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

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

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

3 Limits Throttle: 429
Membership ManagementAssociation ManagementAMSPersonifyRate LimitingQuotas

Limits

API Requests organization
requests
not published
No fixed numeric request-rate limit is documented for the MC Professional API.
List Page Size request
records
100 max per page (default 10)
Documented on paged list endpoints via the pageSize parameter; pageNumber defaults to 1.
OAuth Access Token client
token
expiring bearer token
Tokens are obtained from /oauth/v1/token and expire; clients refresh as needed.

Policies

Paging
List endpoints are paged with pageNumber (default 1) and pageSize (default 10, max 100); iterate pages to retrieve full result sets.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Tenant Isolation
Access is scoped to a single organization's data via per-organization OAuth client credentials on its own {orgId}.memberclicks.net host.

Sources