Accounts to test with
Test accounts keep development data out of your real creator profile. Use a dedicated test creator account as the user of your app, never the creator login you publish with.- Keep the app on your main account. The app, its Client ID and its Client Secret stay in your main account’s Developer Area.
- Register a separate Fanvue account as a test creator. Use a different email address. This account authorises your app and holds the test data: messages, posts and subscriber activity.
- Add more accounts for more roles. A second test account can act as a fan or subscriber, or be invited as a team member to exercise agency behaviour.
- is active
- has full admin privileges
- doesn’t require any payment
Install and open your draft app
Before your app is approved, you can install and run it yourself with real data. While your app has no approved submission, you see Install app on App details, then Open app and Uninstall app once it’s installed. The launched app shows a Delisted pill, whose tooltip tells you to submit the app for moderation to see it on the App Store. Your install is a draft install. It stays out of install counts and App Store analytics. It becomes a counted install when Fanvue approves the submission, and it survives a rejection. Nobody else can reach the draft, because it appears in no listing, search or recommendation.Test webhook delivery
Test on the Events tab delivers a synthetic event to your webhook endpoint. For it to work, you, as the owner, must have authorised your own app with the scope the event requires:
To fix either, authorise your app from your own account, grant the missing scope and retry.
POST /webhooks/test does the same from the API, limited to 30 requests per minute. It rejects the nine deprecated flat events with a 400 validation body, and returns 404 when no active subscription exists for the topic.
Identifiers inside data are prefixed TEST-. purchaser.email and transaction_id are populated in test payloads but are null on production creator.payment.* deliveries. See Test a destination.
Test a fan experience
Only you, as the owner, can reach fan experiences on an unapproved app. Install your draft app, open it and publish an experience from it, then open the experience as the owner. Other fans can’t open it until the app is approved, and until Fanvue approves the experience itself only the creator who published it can open it. See Test before approval.What you can test deterministically
Verify event handling with test and free events first. Only the final money assertions need a real charge.
Test a subscription check
GET /apps/{appUuid}/subscription/me answers a separate test creator with 404 and { "message": "App not found" } until your app is approved. The test creator can still authorise your app through OAuth and call the rest of the API, but an unapproved app is visible to its owner alone, so the subscription lookup finds no app for anyone else.
Before approval:
- Treat that
404as “not entitled” in your gating code, the same asstatus: "none". Your app must handle it anyway, because a404is also what a user gets when the app is not visible to them after launch. - Exercise the entitled path against a stubbed response. Subscription status lists every
statusyour code must handle.
active subscription before then. Once your app is approved, the same call from the test creator returns 200, with status: "none" until that account takes a plan.