Introduction

Testing Your App

The Fanvue API does not provide a sandbox environment. Instead, you test against real Fanvue accounts that you control. This guide explains how to set up a clean testing workflow so your development data stays separate from your real creator profile.

How Testing Works

Your app (OAuth client) lives on your main creator account — that’s where you manage it in the Developer area. But when you test your app’s features as an end user, you don’t want test data mixed into your real profile. The solution is simple: create a separate test creator account that acts as the user of your app during development.

Think of it this way: your main account is the developer, and your test account is the user of your app. This mirrors how real users will interact with your app once it’s live.

Setting Up a Test Creator Account

  1. Keep your app on your main account. Your OAuth application, Client ID, and Client Secret all stay in your main account’s Developer area. This is your development hub — don’t change this.

  2. Register a new Fanvue account as a test creator. Use a different email address to create a separate Fanvue account. This account will act as the end user of your app during testing.

  3. Log into your app as the test creator. When testing your OAuth flow and API calls, authorize your app using the test creator account. All test data (messages, posts, subscriber activity) stays on this account, keeping your main profile clean.

You can create multiple test accounts with different emails to simulate different user scenarios — for example, one as a creator and another as a subscriber.

Best Practices

  • Keep your main account clean. Reserve it for managing your app in the Developer area. Avoid using it as the test user.
  • Manage test creators via the platform and API. Set up realistic profile data on your test accounts so your app behaves as it would in production.
  • Create multiple test accounts for different scenarios. Test with separate creator and subscriber accounts to cover the full range of your app’s functionality.
  • Use separate OAuth apps for development and production. While you can use the same OAuth app for both, creating a dedicated development app with a separate Client ID and redirect URI makes it easier to manage environments independently.

FAQ

Do I need a sandbox API key?

No. Fanvue uses OAuth 2.0 for all API access — there are no standalone API keys. You use the same OAuth flow in development as in production, just with your test creator account as the authorizing user.

Can I use the same OAuth app for testing and production?

Yes, this works. However, best practice is to create separate OAuth apps for development and production once you go live. This lets you use different redirect URIs and keeps your production credentials isolated from your development environment.