API Feedback Mechanism for File Upload Process

Current Issue

Enterprise clients operating Envizi as part of an automated data ingestion pipeline — via S3, SFTP, or client-specific connectors — have no programmatic way to confirm whether a submitted file was received, is processing, loaded successfully, or failed. The only available feedback mechanism is the Data Receipt Report, an automated email sent to contacts with the Data Manager role. This is not consumable by downstream systems, monitoring tooling, or automation workflows.

Envizi’s backend already captures the full file processing lifecycle: delivery confirmation, parse errors, load errors, Records In vs. Records Out, compilation status, and final file status (Loaded, Loaded with Errors, or Error). This data is surfaced in the Files Processed – Accounts & Setup UI and the Data Receipt email, but is not exposed via API.

Proposed Solution

Expose file upload status and processing results via a queryable API endpoint. At minimum, the response should include file status, submission timestamp, Records In/Out, parse error count, load error count, error category (Application, Parse, or Load), and error message detail. A complementary webhook/push notification on processing completion would also address the use case, mirroring the trigger logic already used for the Data Receipt email.

Business Value

For any client operating Envizi with programmatic data ingestion, the absence of an API feedback mechanism forces manual UI verification to confirm file outcomes. This creates operational overhead, delays error triage, and blocks automated remediation workflows. Envizi already captures this data internally — API exposure is a natural extension of existing functionality, not a new data requirement. This is a platform-level capability gap, not a client-specific request, and would benefit all enterprise clients running automated sustainability data pipelines.