Skip to main content
API versioning lets Fanvue introduce improvements without breaking existing integrations. The current version of the Fanvue API is 2025-06-26.
Two things are versioned, and they move independently. This page covers the date version, sent as the X-Fanvue-API-Version header, which pins the response contract. The URL version, the /v1 prefix on the path, selects the shape of the endpoint itself: which query parameters it takes and how a list paginates. /v1 is the current URL version, see Moving to v1.

​
Version header

All API requests must include the X-Fanvue-API-Version header to specify which version of the API you want to use.

​
Error responses

400 Bad Request - When requesting an unsupported version:
410 Gone - When requesting a sunset (removed) version:

​
Reading the reference on either URL version

The API Reference documents both URL versions. The selector in the top bar, next to the logo, switches the whole reference between v1 and v0; it opens on v1. The selector is part of the address, so a link always opens the version it was copied from. v1 pages sit under /v1/, as in /v1/api-reference/overview, and v0 pages keep the unprefixed paths they have always had, as in /api-reference/overview. App Store endpoints (/apps/*) appear only under v0, because they have no /v1 path. Account health is split: the self-scoped /account-health and /account-health/flagged-media are v0 only, while the creator-scoped pair appears under both, as /v1/creators/{creatorUserUuid}/account-health on v1.

​
Dive deeper

Moving from the legacy endpoints to /v1, including the endpoint-by-endpoint mapping, is covered in Moving to v1. For advanced version management strategies, migration patterns, and production best practices, see Version Management Strategies.