Back to recipe
Developer access pending

Developer-review product flow

From recipe to grocery cart, with no retyping.

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

Smoky Chipotle Family Table White Bean Tomato Bake with Herby Yogurt

Serves 4
  • 2 cans cannellini beans, rinsed and drainedPrimary ingredient
  • 1 can fire-roasted diced tomatoesPrimary ingredient
  • 4 cups chopped kalePrimary ingredient
  • 1 small yellow onion, finely dicedPrimary ingredient
  • 1 cup whole-grain breadcrumbsPantry or produce
  • 1/2 cup shredded mozzarellaPantry or produce
  • 1 tbsp extra-virgin olive oilPantry or produce
  • 1/2 tsp kosher saltPantry or produce
  • 1 tsp smoked paprikaPantry or produce
  • 1 tbsp minced chipotle in adoboPantry or produce
  • 1 lime, juicedPantry or produce
  • 1/2 cup plain Greek yogurtPantry or produce
  • 2 tbsp chopped tender herbsPantry or produce

Integration readiness

Built around the review path, not a hard-coded link.

Credentials remain server-only. Development and production hosts, link caching, pantry controls, timeouts, and shopper-safe failure states are all configuration-driven.

01

Two supported payloads

Recipe-specific pages and full-week shopping lists use separate documented endpoints.

02

Quantity normalization

Ingredient display text stays readable while supported units and quantities are mapped for matching.

03

URL reuse

Generated shopping URLs are cached by a hash of the exact payload and refreshed only when content changes.

04

Safe activation

A server-side feature flag and API key are both required before any external request can run.

05

Failure isolation

Eight-second timeouts and neutral errors preserve the user’s plan if the provider is unavailable.

06

Shopper control

No grocery credentials or card data enter WorkLife; the shopper reviews every match after handoff.

Safety and transparency

Designed to keep the shopper in control.

  • No grocery account credentials are collected or stored by WorkLife Meal Plan.
  • The reader deliberately selects the recipe and initiates the handoff.
  • Retailer, product matching, substitutions, totals, and checkout remain with the retail provider.
  • Affiliate disclosures will appear wherever commissionable links are used.
See the community model