Two supported payloads
Recipe-specific pages and full-week shopping lists use separate documented endpoints.
Developer-review product flow
WorkLife Meal Plan now has a working server-side adapter for recipe pages and combined shopping lists. Until developer credentials are issued, this reviewer flow returns the exact normalized request without calling an external service or creating an order.
Selected recipe
Integration readiness
Credentials remain server-only. Development and production hosts, link caching, pantry controls, timeouts, and shopper-safe failure states are all configuration-driven.
Recipe-specific pages and full-week shopping lists use separate documented endpoints.
Ingredient display text stays readable while supported units and quantities are mapped for matching.
Generated shopping URLs are cached by a hash of the exact payload and refreshed only when content changes.
A server-side feature flag and API key are both required before any external request can run.
Eight-second timeouts and neutral errors preserve the user’s plan if the provider is unavailable.
No grocery credentials or card data enter WorkLife; the shopper reviews every match after handoff.
Safety and transparency