For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Join Community
WelcomeDocsAPI ReferenceWebhooksChangelog
WelcomeDocsAPI ReferenceWebhooksChangelog
  • Introduction
    • Welcome
    • Quick Start
    • Testing Your App
  • App Store
    • Publishing Your App
    • Listing Requirements
    • App Subscriptions
    • Deeplinks
  • Authentication
    • Overview
    • Quick Start
    • Implementation Guide
    • Scopes
    • Rate Limits
    • Working With Rate Limits
  • Versions
    • Overview
    • Management Strategies
  • Build With AI
    • Docs For Your LLM
  • Tutorials
    • Example Chatbots
    • Multipart Media Upload
    • Sending Mass Messages
    • Security
  • Integrations
    • n8n
LogoLogo
Join Community
On this page
  • Submissions today are pre-approvals
  • Before you submit
  • Required listing fields
  • Optional listing fields
  • Submission and review
  • Editing after submission reverts to Draft
  • App states
  • Withdrawing an app
  • Suspended apps
  • Related reading
App Store

Publishing Your App

Everything you need to submit an app to the Fanvue App Store, the review flow, and what the different app states mean.
Was this page helpful?
Previous

App Store Listing Requirements

Requirements for being listed — and remaining listed — in the Fanvue App Store.

Next
Built with

This page covers the publishing flow: what you need before you submit, what listing fields are required, how the review process works, and the states an app moves through during its lifetime.

Submissions today are pre-approvals

The App Store is still rolling out public listings. Today, submission goes through the same review against the same policy described on this page — but the outcome is a pre-approval. Approved apps will appear publicly on the App Store once listings launch. See the App Store Introduction for details.

Before you submit

Make sure all of the following are true before you begin the submission flow:

  • You have a Fanvue creator account with KYC completed — see Quick Start prerequisites.
  • Your app is functional end-to-end and has been tested against the live Fanvue API.
  • You have decided on an app type (embedded or off-platform) and, for embedded apps, configured your app surfaces and iframe permissions.
  • You have test credentials ready so reviewers can sign in with Fanvue and exercise your app.
  • Your app meets the Listing Requirements — including SFW presentation, secure credential handling, Terms of Service, Privacy Policy, GDPR compliance, and a data-deletion path for creators.

Required listing fields

Every App Store listing must include:

  • Logo — your app’s icon. Must meet the format, size, and style constraints defined in the Listing Requirements.
  • App name — the name shown on your listing and in the creator’s installed-apps list.
  • Tagline — a short one-line summary that appears in listing previews.
  • Description — longer-form copy explaining what your app does and who it’s for.
  • Preview images — screenshots or visuals shown on the listing page.
  • Test credentials — a username and password reviewers can use to sign in and exercise your app against its integration. Without these, review cannot proceed.

Optional listing fields

These are not required, but filling them in is strongly recommended:

  • “What’s changed in this version” — release notes shown both to reviewers (to explain what changed since the last approved version) and to creators who have the app installed. Recommended on every submission.

Submission and review

When you submit, your app moves into the Submitted state and enters Fanvue’s review queue. Review typically takes several business days and results in one of two outcomes:

  • Approved — your app has passed the policy review. Once public App Store listings launch, approved apps will appear on the store and become installable by creators automatically.
  • Rejected — review feedback will explain why. To address the feedback, create a new draft, make the changes, and resubmit.
Editing after submission reverts to Draft

Modifying any of the listing fields — logo, name, tagline, description, preview images, test credentials, app type, URL, or iframe settings — on a Submitted or Approved app will revert it to the Draft state. You must resubmit the draft and go through review again for the changes to take effect.

Plan edits carefully: for small copy fixes, it may be worth batching them together rather than making several submissions.

App states

StateWho sets itWhat it means
DraftBuilderIn-progress or freshly created. Not visible on the App Store.
SubmittedBuilderReview is in progress. The listing is locked from edits (editing reverts to Draft).
ApprovedFanvue (review outcome)Your app has passed review. Once public App Store listings launch, approved apps will appear on the store and become installable by creators.
RejectedFanvue (review outcome)Review identified issues. The app returns to Draft so you can address feedback and resubmit.
WithdrawnBuilderYou have withdrawn a previously Approved app. The app is disabled, existing OAuth consents are revoked, and the listing is removed. You can resubmit later to relist.
SuspendedFanvueFanvue has suspended the app (for policy, security, stability, or other reasons). The listing is disabled. Only Fanvue can restore a suspended app — reach out in the Fanvue builder community on Discord for details.

Withdrawing an app

Withdrawing is the builder-initiated way to take an approved app down. Use this if:

  • You no longer want to operate the app.
  • You need to take the app offline while you work on a significant update.
  • You’re sunsetting the integration.

Withdrawing revokes all existing OAuth consents — users will need to reauthorise if you later resubmit and relist.

Suspended apps

Only Fanvue can suspend or restore an app. If your app is suspended, review any communication sent to you, address the underlying issue, and reach out in the Fanvue builder community on Discord to discuss restoration.

Related reading

  • App Store Introduction — high-level overview of the App Store and the build-to-publish journey.
  • App Types — embedded vs off-platform, app surfaces, and the listing × payment-rails matrix.
  • Listing Requirements — the full policy baseline every listed app must meet.
  • Managing your OAuth client secret — lifecycle and rotation guidance for the credentials generated when you create your app.