I already have a Python-based OCR service on my own server that extracts invoice data and returns a clean JSON response. What I now need is the FileMaker side built out—from user upload through to review and storage—so everything runs smoothly inside FileMaker Pro. The integration will call the existing REST endpoint over HTTP POST, handle OAuth, pass the PDF/JPG files, then capture and parse the JSON that comes back. From there the data must populate our invoice header and line-item tables, set a processing status, and log any errors with a timestamp and user ID. Because this module will sit in everyday production, I also need intuitive layouts: one for importing, one for quick review and manual corrections, plus a searchable list/detail screen. All scripting should be maintainable and rely on native FileMaker functions (cURL, JSON functions, script parameters, etc.) wherever possible. Deliverables • FileMaker scripts that upload the selected file, post it to the API, receive the JSON, and create/update records. • Clean layouts for import, review/correction, and invoice list/detail. • Status logic: Processed, Needs Review, Error—with visual cues. • Lightweight logging table and routines. • Brief implementation notes so my in-house team can extend or troubleshoot later. Acceptance criteria 1. A user drags an invoice into FileMaker, clicks “Process,” and sees header and line items filled without leaving FileMaker. 2. If the API flags an issue, the invoice is routed to the review layout automatically. 3. All network calls authenticate via OAuth and fail gracefully with a recorded error. 4. No unhandled script errors appear during normal use. If you have solid experience linking FileMaker Pro to external REST services and building production-ready UI, this should be a focused, satisfying build.