> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ofauth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test your integration

> Check your app in Sandbox, then try an account you control in Test.

Start with sample accounts in Sandbox. Once your app works, use Test to check it with a real OnlyFans account you control. Each mode has its own client ID, secret, and accounts.

## Start in Sandbox

Run the [Quickstart](https://docs.ofauth.com/v3/setup/quickstart.md) with the Sandbox client ID and secret. Confirm that your app completes sign-in and approval, then shows the sample profile.

Sandbox does not contact OnlyFans. Use it to build your screens and check request handling. Common writes, such as sending a message or renaming a Vault list, are kept for 24 hours so later reads show them; see [Environments](https://docs.ofauth.com/v3/api-reference/environments.md#writes-are-kept-for-24-hours). A Sandbox response does not prove that a change would succeed on a real account.

## Validate real account behavior in Test

1. In the OFAuth dashboard, choose an account your organization controls for use in Test.
2. Open your integration's **Test** settings.
3. Add the same callback URL used in Sandbox.
4. Save the Test client ID and secret.
5. Replace the Sandbox values in your app's settings with the Test values.
6. Restart the app.
7. Sign in as a member of your organization and approve access to the chosen Test account.
8. Read the profile and check that its name and username match that account.

Your client ID selects Sandbox, Test, or Live. The API hostname stays the same. Accounts and tokens do not move between modes. See [Environments](https://docs.ofauth.com/v3/api-reference/environments.md) for Test limits and settings.

## Check recovery before launch

As you add features, check how your app responds when access changes:

| Check | Your app needs to… |
| - | - |
| The owner declines access | Let them start again. Do not assume you have permission. |
| The access token expires | Refresh on the backend and persist the new access token; the refresh token stays the same. |
| An account is removed | Stop using it and update the account list. |
| A required permission is missing | Ask for the additional access the feature needs. |
| A request fails temporarily | Retry only when the operation can safely be repeated. |

Use the [token reference](https://docs.ofauth.com/v3/api-reference/link/tokens.md) and [error handling guide](https://docs.ofauth.com/v3/reference/error-handling.md) as you implement these checks.

When your app works with the Test account, continue to [Go live](https://docs.ofauth.com/v3/setup/integration-checklist.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.