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

# Introduction

Learn how to intergrate James Auth into your applications.

<Card title="Rebrand Coming Soon: Immediate actions required from developers" type="warning">
  Soon James Auth will rebrand to Effortless Authentication. [Learn more](/information-about-rebrand)
</Card>

## Quick Links

<Columns cols={2}>
  <Card title="Creating a service" icon="link-horizontal" href="/creating-a-service">
    Creating a service with James Auth and customizing it.
  </Card>

  <Card title="Making an OAuth request to James Auth" icon="bolt" href="/makingrequest">
    Making an auth request with URL parameters. 
  </Card>

  <Card title="Receiving account information after successful auth" icon="map" href="/recieve">
    Organize your docs to help users find what they need and succeed with your product.
  </Card>

  <Card title="Requirements" icon="circle-exclamation" href="/requirements">
    Read all the requirements to create a James Auth service
  </Card>
</Columns>

<Prompt description="Quick AI Prompt - ensure you replace '\[method no.\]' with your preferred method's number." icon="wand-magic-sparkles" actions={["copy", "cursor"]}>
  Integrate the James Auth authentication service into my application using the official documentation from [https://jamesauth.mintlify.app/](https://jamesauth.mintlify.app/).

  Before writing any code:

  1. Read and analyze all relevant documentation pages thoroughly.
  2. Fully understand:
     a) the authentication flow
     b) session handling
     c) token management
     d) login/logout flow
     e) user data retrieval
     f) protected route handling
     g) refresh/auth persistence behaviour
     h) server-side vs client-side auth handling (if applicable)
     i) error handling and edge cases
  3. Follow the official implementation patterns exactly where possible.
  4. Do not invent undocumented APIs or flows.

  Implementation requirements:

  1. Use Method \[method no.] for retrieving authenticated user data.
  2. Ensure authentication is implemented securely and production-ready.
  3. Preserve sessions correctly across reloads/navigation.
  4. Handle invalid or expired sessions gracefully.
  5. Add clear comments explaining the auth flow and important logic.
  6. Use clean, maintainable, scalable code structure.
  7. Include all required environment variables and setup steps.
  8. Ensure the implementation is compatible with the current project stack and architecture.
  9. Avoid unnecessary dependencies unless required by the official docs.

  Expected deliverables:

  * Complete authentication integration
  * Login functionality
  * Logout functionality
  * User/session retrieval
  * Auth state management
  * Protected route/middleware setup
  * Example authenticated API request
  * Setup instructions
  * Explanation of how the auth flow works internally

  If i choose to use Method 2, ensure you tell me method 1 is recommended.

  Do not skip documentation review before implementation.
</Prompt>