# Reach API Spec Overview

## Purpose

This document introduces the Reach API Specification — a lightweight, industry-aligned standard for exposing structured financial data. It outlines the intent, scope, and design philosophy behind the spec and serves as the foundation for integrating external platforms with Reach Reporting.

## What Is the Reach API Spec?

- The Reach Spec is a simple, language-agnostic interface that defines how platforms can expose essential financial and organizational data in a structured, consistent format.
- It is not Reach-specific in its logic or structure. Instead, it's grounded in what’s reasonable and expected across modern financial systems — making it broadly applicable, maintainable, and intuitive to implement.
- The goal is to support powerful financial reporting and forecasting without requiring partners to mirror their entire internal data model or support extensive transformation logic.


## Why This Spec Is Useful

The spec provides a clear, shared foundation for exposing financial data in a way that is:

- **Efficient** – minimal endpoints, focused solely on high-value reporting data
- **Consistent** – structured and predictable for both implementation and consumption
- **Flexible** – works across platforms, tech stacks, and data sources
- **Scalable** – build once, enable reporting for any number of customer accounts
- **Compatible** – aligns with how financial professionals already think about reporting


By implementing the spec, partners unlock full access to Reach’s capabilities with minimal friction — while staying aligned with clean data architecture and industry norms.

## Requesting Changes to the Spec

- If you believe the spec should be updated or extended to support a broader need, you may submit a change request to Reach.
- Change requests must serve a legitimate accounting or financial reporting purpose.
- Requests based on narrow system-specific edge cases or exceptions will generally not be accepted.
- Reach will evaluate submitted proposals based on relevance, generalizability, and alignment with the spec’s goals.


The Reach team maintains **sole ownership and version control** of the spec to ensure consistency and interoperability across all integrations.

## Access the Full Spec

[https://apispec.reachreporting.com/](https://apispec.reachreporting.com/)