A browser watchlist for option snapshots
Save contract identifiers in this browser and review the fields returned by the configured market-data API. Quotes, trades, session data, IV and Greeks can be missing or delayed. A saved row remains visible when no snapshot is returned, so missing data is not mistaken for a zero price or a removed contract.
Build and check a list
- Search an underlying ticker. The search reads the first 50 unexpired contract references ordered by expiry; it does not load more pages.
- Add selected contracts. The page requests up to 250 saved identifiers in a snapshot call. Adding or removing a contract reloads the current list; manual Refresh is also available.
- Compare available fields. Reference Price uses daily-bar close first, then last trade, quote midpoint, then session close. These are different observations, not a guaranteed executable price; alerts use this same priority.
- Set a price, IV, delta, gamma, theta or vega threshold using the bell. IV uses decimals: enter 0.50 for 50%. Greek thresholds use the provider’s reported units. Conditions are strictly above or below, so equality does not match.
What a local alert means
The page checks enabled conditions after successful refreshes. A newly matching condition can attempt a browser notification and records its match time. It re-arms after a successful check that does not match, or after a reload. The first observation may already satisfy the condition; this is not proof that a price crossed the threshold between checks.
Notifications require browser support, permission, and an active page. Operating-system settings, background throttling, sleep or closing the page can prevent checks or delivery. There is no server monitor, service-worker push, email, SMS or order execution. A recorded match is not a delivery receipt and should not be used as a stop order.
Refresh frequency is not data freshness
When enabled, the browser requests snapshots every 30 seconds without a market-hours restriction. The server can reuse snapshots for one hour and upstream delays may apply. Retrieval time is not quote time; a failed refresh preserves older displayed rows with a warning and does not evaluate alerts.
Storage and privacy boundaries
The watchlist and alert rules use this browser’s local storage. They are not synchronized to other devices. Clearing site data, private browsing limits or blocked storage can prevent persistence. Search symbols and saved contract identifiers are sent to Pineify’s API to obtain market data; local persistence does not mean all processing stays on the device.
References: Massive unified snapshot fields and limits and browser notification requirements.