Ko-fi · Rate Limits

Ko Fi Rate Limits

Ko-fi's only developer surface is an outbound payment webhook, so traditional request-rate limits do not apply - your service does not call Ko-fi. Ko-fi POSTs a notification to your configured URL only when a payment happens, so the effective "rate" is simply your payment volume. Ko-fi does not publish numeric webhook delivery limits, retry counts, or timeout values. Because there is no public REST API, there are no per-account or per-endpoint request quotas to document.

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

It captures 2 rate-limit definitions, measuring events and requests.

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

Tagged areas include Creator Economy, Webhooks, Payments, and Rate Limiting.

2 Limits Throttle: not applicable (inbound webhook; you return 200 to Ko-fi)
Creator EconomyWebhooksPaymentsRate Limiting

Limits

Payment Webhook Delivery account
events
event-driven (one POST per payment)
Ko-fi POSTs to your URL only when a payment occurs; no fixed numeric cap is published.
Public REST API Requests account
requests
not applicable
Ko-fi does not expose a public REST API, so there is no outbound request quota.

Policies

Idempotency
Ko-fi may deliver a webhook and does not document retry semantics; dedupe on kofi_transaction_id or message_id so re-delivered events are processed once.
Verification
Reject any webhook whose verification_token does not match the token on your Ko-fi webhooks page before doing any processing.
Fast Acknowledgement
Return an HTTP 200 quickly and offload heavy work to a background job so the webhook POST does not time out.

Sources