Skip to navigation

Test your integration

Test a rejected login as carefully as a successful one. Your app should explain the problem and keep protected actions unavailable.

Run these checks

Try thisWhat to check
Sign in with a valid test identityYour app opens the intended features and shows the correct user data
Enter the wrong password or keyThe app stays signed out and displays the returned reason
Ban the identity after loginA session check rejects access and your app responds appropriately
End the session from the dashboardThe old session cannot keep making protected requests
Disconnect the networkThe app remains responsive and follows its access deadline/offline policy
Sign out, then sign in as someone elseThe previous customer’s data and access are cleared

Check the result, not the message text

Use the success indicator and stable response code for your application’s decisions. Display the message to the customer. Messages can be customized, so comparing an English sentence is not a reliable access check.

Keep the interface responsive

While a request is waiting, try typing and moving the window. Avoid blocking the UI thread to wait for a result. Follow your language’s SDK examples for callbacks or asynchronous calls, and update controls on the UI thread where your framework requires it.

Check the version you distribute

Test the built application and the SDK package you will ship, not only the source in your editor. Verify the API address, AppKey, version and verification-key configuration. Remove test credentials from screenshots and logs.

Use SDK methods for language examples and API Reference for direct HTTP integrations.