# Check Network Request Headers

## What We Need to Find

We need to see how Filevine sends authentication tokens in API requests.

## Steps:

1. **Open DevTools → Network tab**
2. **Filter by "XHR" or "Fetch"**
3. **Find a request to Filevine API** (like `/api/projectHub/search` or `/api/orgs`)
4. **Click on the request**
5. **Go to "Headers" tab**
6. **Look at "Request Headers" section**

## What to Look For:

### Option 1: Authorization Header
```
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...
```
If you see this, we can intercept it!

### Option 2: Cookie Header
```
Cookie: .AspNet.ApplicationCookie=CfDJ8...; other-cookies...
```
If you see this, Filevine uses cookies (HTTP-only cookies can't be read by JS, but we can see them here)

### Option 3: Custom Headers
```
x-fv-token: ...
x-auth-token: ...
```
Any custom headers with tokens

## What to Report:

Please share:
1. **Do you see `Authorization: Bearer ...` header?**
2. **What does the `Cookie` header contain?**
3. **Any other auth-related headers?**

This will tell us exactly how to extract the token!
