Friendbuy · Rate Limits

Friendbuy Rate Limits

Friendbuy does not publish fixed numeric rate limits for the Merchant API in its public developer documentation. The API is a server-to-server integration used for customer sync, event tracking, referral-link generation, analytics reads, and loyalty ledger operations; practical throughput is governed by the account's plan and by Friendbuy's operational limits rather than by a documented per-minute request cap. The authorization token obtained at POST /authorization is short-lived (the response carries an `expires` timestamp), so clients should cache the token until near expiry and re-auth rather than calling /authorization on every request.

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

It captures 4 rate-limit definitions, measuring requests, token, and rows.

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

Tagged areas include Referral Marketing, Loyalty, Rewards, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Referral MarketingLoyaltyRewardsRate LimitingQuotas

Limits

Merchant API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Merchant API.
Authorization Token Lifetime account
token
short-lived (see expires timestamp)
Cache the Bearer JWT until near its expires time; re-authorize rather than per-call.
Referral Link Generation account
requests
use batch endpoint for volume
postPersonalReferralLinkBatch generates many links per request to reduce call count.
Analytics Pagination account
rows
paginated via pageToken
Analytics endpoints return pages; follow nextPageToken to read full date ranges.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Token Caching
Reuse the Bearer token across requests until near expiry to avoid unnecessary /authorization calls.
Batching
Prefer batch endpoints and paginated reads to keep request volume low.

Sources