Data Exports

Overview

Fortress also supports integration through scheduled data exports delivered via SFTP. This is currently the best option for downstream analytics workflows that need bulk data in files instead of API calls.

Upon request, Fortress provisions an SFTP folder for each organization to access its exported data. Refresh cadence varies based on integration needs.

Architecture

The following diagram shows the data export integration flow.

Export Delivery Model

Fortress supports two export delivery modes:

  1. Full load A full snapshot file for a topic (for example, Activities or Work Orders) is delivered.

  2. Change detect (CDC) A full snapshot file is delivered first. After that, additional files include only row-level changes for that topic.

Folder Structure

Exports are organized by organization and topic folder.

{organizationId}/public/exported_activities/LOAD.csv
{organizationId}/public/exported_workorders/LOAD.csv
{organizationId}/public/exported_..../LOAD.csv

Equivalent parquet exports use the same path pattern with .parquet file extension.

Example Topic Folders

Based on a typical organization export location, you may see folders such as:

{organizationId}/public/exported_activities/
{organizationId}/public/exported_affordablecontracts/
{organizationId}/public/exported_amenities/
{organizationId}/public/exported_applications/
{organizationId}/public/exported_applicationstatuschanges/
{organizationId}/public/exported_balances/
{organizationId}/public/exported_buildings/
{organizationId}/public/exported_certificationcustomers/
{organizationId}/public/exported_certificationdocuments/
{organizationId}/public/exported_certificationreviewstatuschanges/
{organizationId}/public/exported_certifications/
{organizationId}/public/exported_customers/
{organizationId}/public/exported_deposits/

Certifications Export

The exported_certifications topic provides affordable certification data including compliance status, unit and tenant details, program info, and financial amounts. See the Certifications Export page for full field documentation, type mappings, and soft-delete behavior.

SFTP Access Coordination Checklist (Fulson)

Use the following operational checklist during Fulson onboarding:

  1. Confirm Fulson contact and collect SSH public key from Nathan Mata (nathan@fulsonhousing.com).
  2. Coordinate with Travis Hoover to install/validate the public key on the organization SFTP endpoint.
  3. Verify Fulson can read LOAD plus CDC files from {organizationId}/public/exported_certifications/.
  4. Validate row-level output in a non-production or test-safe environment before production handoff.
  5. Record any limitations (for example, certification type values that do not map to MI/AR/IR) and share them with Fulson.

Example Files Per Topic

Full-load and CDC files for a topic might look like:

{organizationId}/public/exported_activities/LOAD.csv
{organizationId}/public/exported_activities/20260601-010000000.csv
{organizationId}/public/exported_activities/20260601-020000000.csv
{organizationId}/public/exported_workorders/LOAD.parquet
{organizationId}/public/exported_workorders/20260601-010000000.parquet

In CDC mode, incremental files follow YYYYMMDD-HHMMSSfff ordering.

File Formats

Exports can be delivered in either of the following formats:

  • csv
  • parquet

Typical Integration Flow

  1. Fortress provisions the organization SFTP location.
  2. Consumer reads initial full-load files per topic.
  3. Consumer processes ongoing CDC files for incremental updates.

Getting Started

  1. Contact Fortress to enable Data Exports for your organization.
  2. Confirm required topics and preferred file format (csv or parquet).
  3. Align on refresh cadence and CDC enablement during onboarding.
  4. Implement ingestion using the CDC processing guidance.

See the Change Data Capture (CDC) page in this section for operational details, including operation precedence and row ordering requirements.