Skip to main content
V3 returns errors in two formats. The token and revoke endpoints use the OAuth format defined by RFC 6749. Everything under /v3/access, /v3/vault-plus, and /v3/linked-accounts uses the API error response.

API error response

API error codes

Validation errors on request bodies and query parameters return 400 with the same JSON format and a descriptive error, such as invalid_request. When OnlyFans rejects a request, the error is one of provider_request_rejected (do_not_repeat or check_request), provider_resource_not_found (check_resource), linked_account_reconnect_required (reconnect_linked_account), rate_limited (retry), or transient_provider_failure (retry).

Recovery actions

OAuth endpoint errors

POST /v3/link/token and POST /v3/link/revoke return RFC 6749 bodies.
reason and recovery appear only when the integration is deleted, its plan is unavailable, or it is suspended (client_deleted, developer_plan_unavailable, security_suspended).

Callback errors

The authorization redirect can return error=access_denied (user declined or cancelled) or error=invalid_request (the request expired or was malformed). Both include your original state.

Handling pattern

The SDKs expose API errors as exceptions with the error code, recovery action, and request ID. This TypeScript example uses the client from SDK setup. Retry rules are built into the SDK; follow Handle failed requests when deciding what your app does next.
TypeScript SDK