Amazon orders integration parked (2026-05-22)

DARE.CO.UK · PARKED SKETCH · 2026-05-23

Mirrored from ~/.claude/.../memory/project_amazon_orders_integration_parked.md. This is a design sketch parked for future build — read for context, not as a current deliverable.

No buyer-side API; path forward is Fastmail JMAP email-scrape of “Your Amazon.com order” subjects (same template as Sense/Harvest/eBay/Privacy parked sketches). Sanctioned alternative is amazon.com → Privacy → Request Your Data (manual quarterly ZIP).

Amazon orders → pa.gf.cx integration (parked)

Asked 2026-05-22. Dan: “does amazon allow developer access to your account, for pulling down past purchases?”

Answer: No. Amazon has aggressively closed off buyer-side API access: - SP-API (Selling Partner) — sellers only - PA-API (Product Advertising) — affiliates only, no personal data - Amazon Ads API — advertisers only - MWS — deprecated, sellers only anyway

Old unofficial libraries (amazon-buyer-api, amzn-orders-scrape) are all broken/abandoned.

Three real paths

1. GDPR “Request Your Data” export — sanctioned, slow - amazon.com → Account → Privacy → Request Your Data → "Your Orders" - Button-click triggers email with ZIP ~24-72hrs later - Complete history; CSV format (date, items, $, ship-to, payment method) - Cadence: quarterly manual → drop via dropzone → parser

2. Fastmail JMAP email-scrape — most aligned with stack ⭐ - Subject pattern: “Your Amazon.com order #XXX-XXXXXXX-XXXXXXX of…” (stable across years) - JMAP text filter → extract order #, items, total, ship-to from body - Already in active use for vendor correspondence (DDG aliases + sieve) - Limitation: only as far back as Fastmail retention; misses combined-shipment emails - Best fit for pa.gf.cx auto-population (equipment, contractors, claim re-orders)

3. Playwright against amazon.com/your-orders — ToS-violating, fragile - Requires session cookie; Amazon detects + blocks every 6-12 months - 3rd-party services (Rocketbot, BuyMore) all wrap this approach - Skip unless GDPR delay is genuinely unacceptable

Resume conditions

• pa.gf.cx/equipment record needs auto-population from “I bought it from Amazon” history
• Claim re-order search (e.g. “did I already buy a replacement Chapin sprayer after the loss?” — first hit 2026-05-22)
• Sell/keep decisioning needs “when did I buy this” answered without hand-typing

Build path when resumed

1. Reuse Fastmail JMAP creds (already in op://Code Shared/Fastmail JMAP)
2. Sibling script to pa_dropzone_apply.py — pa_amazon_orders_pull.py
3. Search from:auto-confirm@amazon.com + subject:"Your Amazon.com order" since YYYY-MM-DD
4. Parse body → JSON sidecar at pa/_data/amazon-orders.json
5. pa records query the sidecar; equipment landings auto-show purchase history

Cross-refs

• project_harvest_api_integration_parked.md — sibling pattern
• project_ebay_seller_api_integration_parked.md — sibling pattern
• feedback_fastmail_aggressive_sieve_trash.md — JMAP text filter usage
• feedback_capture_at_source_durable_substrate.md — verbatim email → substrate principle