Test and go live

Test the whole flow with your own account, then check a few things before you launch.

Test with your own credits

Sign in to your app with your own rNet account. Your test requests are paid from your own wallet, the same way your users' requests are paid from theirs. New accounts include 2,000 credits; buy more in the Developer Console under Billing.

Register a separate app for local development with a http://localhost redirect URI, so you never change your production app's settings while testing.

Launch checklist

• The Client secret is only on your server, in an environment variable, and not in your repository.
• Your production app uses an HTTPS redirect URI that exactly matches your callback route.
• You check the state value on every callback.
• Tokens are stored server-side, and you save the new refresh token after every refresh.
• On 401 you refresh and retry once; if refresh fails you ask the user to connect again.
• On 402 you tell the user they are out of credits and link them to their Credit Wallet.
• Your button says Connect with rNet and follows the button guidelines.
• You considered running prompts through Context Eraser.

After launch

Watch requests, credits and per-app usage in the Developer Console under Usage. Want your app listed on the Apps page? Get in touch.