Auth Aware

Auth Aware provides multiple authentication strategies to streamline testing authenticated routes in Routesy. A status indicator in the sidebar shows your current session state: idle, authenticating, authenticated, or error.

Sanctum #

If you have ever tested Laravel Sanctum through Postman, you have already faced a typical "problem" associated with how Laravel Sanctum works: having to make a request to /sanctum/csrf-cookie before logging in. Routesy solves this easily by allowing you to define authentication aspects based on "Sanctum", where you must specify the data used for it:

The feature consists of opening an authenticated session easily and effectively:

1. First, Routesy will make a request to the CSRF cookie endpoint
2. Then, Routesy will make the login request
3. After that, requests protected by auth:sanctum will work normally

The CSRF cookie endpoint, login endpoint, and logout endpoint are all configurable in the Auth Aware settings. You can also configure custom login fields, it is not limited to email and password. After opening the session, you can interact with it through sidebar shortcuts:

Note: Sanctum authentication is not available when using the MCP Server, as it requires an active application window to manage cookies and session state.

Bearer Token #

You can also authenticate using a Bearer Token. Simply provide your token in the Auth Aware settings, and Routesy will automatically include it as an Authorization: Bearer <token> header in all your requests.

Basic Auth #

For APIs that use HTTP Basic Authentication, you can configure a username and password in the Auth Aware settings. Routesy will include the credentials in the Authorization header for each request.