Skip to main content
V3 has two error shapes. The token and revoke endpoints follow RFC 6749. Everything under /v3/access, /v3/vault-plus, and /v3/linked-accounts uses the runtime envelope.

Runtime envelope

Runtime error codes

Validation errors on request bodies and query parameters return 400 with the same envelope and a descriptive error, such as invalid_request. When OnlyFans rejects an admitted 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 for integration lifecycle problems (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

Node.js