How to Fix Bitwarden Send Link Issues

In this tutorial, you'll learn about How to Fix Bitwarden Send Link Issues. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

You shared a Bitwarden Send link but the recipient reports "Link not found" or "This send has expired." Deletion schedule or access count settings caused premature expiration.

The Wrong Way

// Creating a Send without configuring expiration
send = await bitwarden.send.create({ text: 'Secret message' });
// Default: 1 access, 7 days expiry

Default settings are restrictive. The link may expire after one view or before the recipient opens it.

The Right Way

Step 1: Configure Send options carefully

# In the web vault or CLI:
bw send create --text "Secret message" \
  --name "API Key for John" \
  --max-access-count 5 \
  --deletion-date "2026-07-24" \
  --expiration-date "2026-07-01"

Step 2: Choose the right deletion schedule

# Options:
# - Deletion date: hard delete after this date
# - Expiration date: link stops working after this date
# - Max access count: link auto-deletes after this many views
# For most cases: set deletion date to 30 days, max access to 10

Step 3: Set a password for the Send

bw send create --text "Confidential" \
  --name "Secret" \
  --password "shared-over-phone"
# Recipient must enter this password to view the content

Step 4: Share the link securely

# The link looks like:
# https://vault.bitwarden.com/#/send/ABC123def456
# Send the link via one channel (email)
# Send the password via another channel (phone/SMS)

Bitwarden Send created — link valid for 30 days, 5 access limit, password-protected.

Prevention

• Set deletion dates at least 30 days in the future for important shares.
• Always use a password for sensitive content (API keys, credentials).
• The secure-link pattern is used by DodaZIP's encrypted share feature — time-limited, access-limited, password-protected.

Common Mistakes with send link

1. Using foldl instead of foldl' causing stack overflow on large lists
2. Forgetting deriving (Show, Eq) on custom data types needed for debugging
3. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable

These mistakes appear frequently in real-world BITWARDEN code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ