API and export documentation

Access and availability

This is public documentation, not a public self-service API. A documented schema does not grant access to records. Use an approved WorkOS-backed workspace session and the permissions enabled for your role. Private application endpoints are not a customer integration contract.

In-product

Research lead CSV download, within the visible authorized queue.

Documented

The separate workspace CSV handler schema below. This is not a promise of public availability.

Request-scoped

Customer API access, bulk delivery, and custom exports require a scope and availability review. No public API keys, rate allowance, or delivery SLA are offered here.

1. Sign in to your approved workspace and open Research leads at /app/signals.
2. Review the loaded queue and select the diligence-category filter you need.
3. Choose Export lead queue. The button requires the report.generate capability and at least one visible row.

The queue loads up to 100 rows from its authorized lead source or its signal-card fallback. The CSV contains the visible subset of those 100 loaded rows, not the entire ranked run or every record in a market. The two sources are not combined into a larger export. This download does not paginate through the rest of a saved review.

Filename: acren-research-leads-YYYY-MM-DD.csv. Format: UTF-8 CSV with a header row and quoted values.

Separate workspace CSV contract

Documented / Request-scoped availability

The existing workspace CSV handler returns at most 1,000 rows. It is not the file produced by the current Research leads button. Confirm delivery and entitlement before building against this schema; it is not advertised here as a public API endpoint or a self-service bulk export.

Customer requests require verified approved access, an active workspace, and an active display-approved feed with can_export enabled. Customer rows are scoped to that workspace and approved for display; demo and synthetic signal rows are excluded. Selected signal IDs and supported filters narrow the export, but this handler does not provide a paginated full-market download.

Stable references and identifier scope

Use Acren property and entity record identifiers for repeat references when they are supplied; retain the identifier type and namespace. Source refreshes and identity reconciliation do not make every source identifier interchangeable or permanently immutable. These are reference fields used across the product, not additional columns promised in either CSV above.

Acren does not guarantee a universal loan or transaction identifier across jurisdictions and sources. Keep the original source record identifier, jurisdiction, and source dates when supplied, and verify links before joining records.

Use an exported file locally

Illustrative CSV only, not a customer record. The example ID is a placeholder, not a resolvable property.

"property_id","property","priority","confidence","next_step"
"example-property-id","Illustrative property","Needs review","","Review source evidence"

Read the downloaded file with Python's standard CSV parser. A blank value remains unknown, not zero. Keep identifiers as strings.

import csv

with open("acren-research-leads-2026-08-30.csv", newline="", encoding="utf-8") as file:
    for row in csv.DictReader(file):
        property_id = row["property_id"] or None
        confidence = float(row["confidence"]) if row["confidence"] else None
        print(property_id, confidence, row["next_step"])

Import text fields as text, not spreadsheet formulas. Keep the original file, export date, and selected scope with your analysis. An export timestamp is not a source effective date. Missing fields, confidence labels, and research priorities do not replace source verification. Downloads do not grant redistribution rights or permission to use records outside your approved scope.