Skip to content

docs: add auth token troubleshooting #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
saurabhhhcodes wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add auth token troubleshooting #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -325,6 +325,30 @@ apidrift **never stores your actual data** — only the shape (field names + typ

---

## Troubleshooting

### Authorization header looks empty or unresolved

If apidrift warns that your `Authorization` header looks empty/unresolved, `${STAGING_TOKEN}` or `${PROD_TOKEN}` likely resolved to an empty value before the request was sent. Check that your token names match the placeholders in `apidrift.config.json`.

For bash/zsh:

```bash
export STAGING_TOKEN="your_token_here"
export PROD_TOKEN="your_token_here"
```

For PowerShell:

```powershell
$env:STAGING_TOKEN = "your_token_here"
$env:PROD_TOKEN = "your_token_here"
```

You can also place the variables in a `.env` file in the same directory where you run `apidrift`; this is usually the project root that contains `apidrift.config.json`. Keep `.env` out of git so real tokens are not committed.

---

## Snapshot Storage

Snapshots are stored globally at `~/.apidrift/snapshots/` — accessible from any project on your machine.
Expand Down