> This page is for version V3 - Beta (default).
> For other versions, use one of these documentation indexes:
> - V3 - Beta (default): https://docs.authlyx.dev/v3/llms.txt
> - V2 - Legacy: https://docs.authlyx.dev/v2/llms.txt
> - V1 - End of support: https://docs.authlyx.dev/v1/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.authlyx.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.authlyx.dev/_mcp/server.

# Test your integration

> Check successful sign-in, rejected access and session changes before sharing your app.

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 this                               | What to check                                                             |
| -------------------------------------- | ------------------------------------------------------------------------- |
| Sign in with a valid test identity     | Your app opens the intended features and shows the correct user data      |
| Enter the wrong password or key        | The app stays signed out and displays the returned reason                 |
| Ban the identity after login           | A session check rejects access and your app responds appropriately        |
| End the session from the dashboard     | The old session cannot keep making protected requests                     |
| Disconnect the network                 | The app remains responsive and follows its access deadline/offline policy |
| Sign out, then sign in as someone else | The 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](/v3/sdks/methods/initialize) for language examples and [API Reference](/v3/api-reference) for direct HTTP integrations.