Expiry Notifications

CIFP can send you an email, an SMS, or both whenever a secret is approaching its expiry date. Notifications are sent per-proxy and are deduped — you will receive each alert exactly once per configured lead time, no matter how many times the scheduler runs.

Notifications currently cover secrets only — API keys, tokens, and passwords added via the Secrets panel. Proxy credentials (the username/password pairs used to authenticate clients connecting to the proxy itself) do not yet trigger expiry notifications, even if given an expiry date.

Configuring Notifications

Open the proxy detail page and click the Notifications tab. From there you can:

1. Toggle notifications on or off
2. Enter an email address to receive HTML email alerts
3. Enter a phone number (E.164 format, e.g. +15558675309) to receive SMS alerts
4. Choose one or more lead times — how far ahead of expiry you want to be notified

Lead Times

A lead time defines how far in advance of expiry a notification is sent. The scheduler checks every hour and fires the appropriate alert as soon as the time-until-expiry drops below each configured threshold.

The default configuration sends two notifications: one at 7 days and a final reminder at 1 day. You can enable as many lead times as you like — each one fires independently and is tracked separately.

How Deduplication Works

Every notification sent is recorded in a local log on the proxy machine. Before sending, the scheduler checks whether the same (item name, lead time, channel) combination has already been sent. If it has, the alert is skipped.

This means:

• A secret with 2w and 1d lead times configured will trigger at most two emails and two SMS messages per expiry cycle.
• If your proxy restarts or the scheduler runs multiple times in the same window, no duplicate alerts are sent.
• The dedup log is per-proxy and stored locally — it is not synced to the control plane.

What the Notifications Look Like

Email

Email notifications are sent via Resend from the CIFP notification address. The email includes:

• The secret name
• Exact expiry date
• Days remaining (colour-coded: amber → orange → red as expiry approaches)
• A Renew Now button linking directly to your proxy dashboard

The urgency colour escalates automatically:

SMS

SMS messages are sent via Twilio and kept intentionally brief:

[CIFP] OPENAI_API_KEY expires in 6 day(s). Renew at https://cifp.vril.dev

The message includes the item name, days remaining, and the renewal link. One SMS is sent per item per lead time — the same deduplication rules as email apply.

What Has an Expiry Date?

Only secrets with an explicit expiresAt value set are covered. Secrets with no expiry date never trigger notifications. Set expiresAt when creating or updating a secret via the dashboard or API — see the Secrets guide for details.

API Reference

Notification settings are managed through the CIFP API, authenticated with your CIFP API key.

Get notification settings

curl https://cifp.vril.dev/api/proxies/proxy-id/notifications \
  -H "Authorization: Bearer cifp_your_api_key"

{
  "enabled":   true,
  "email":     "you@example.com",
  "phone":     "+15558675309",
  "leadTimes": ["1w", "1d"]
}

Update notification settings

curl -X PUT https://cifp.vril.dev/api/proxies/proxy-id/notifications \
  -H "Authorization: Bearer cifp_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled":   true,
    "email":     "you@example.com",
    "phone":     "+15558675309",
    "leadTimes": ["2w", "1w", "1d"]
  }'

No Content

Field reference

Troubleshooting