# Inspect Network Requests for Authentication

## Step 1: Check Network Tab for Authorization Headers

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

**What to look for:**
- `Authorization: Bearer <token>` ← **This is what we need!**
- `Cookie: .AspNet.ApplicationCookie=...`
- Any `x-fv-*` headers
- Any custom headers with tokens

## Step 2: Check Response Headers

Also check the **Response Headers** for:
- `Set-Cookie: ...` (might contain tokens)
- Any custom headers

## Step 3: Check Request Payload

If it's a POST request, check the **Payload** tab to see if tokens are sent in the body.

## What We Need

Please share:
1. **A screenshot or copy of Request Headers** from any API call
2. **The URL of the API endpoint** you're inspecting
3. **Any `Authorization` header** you see

This will tell us exactly how Filevine sends authentication tokens.
