API specification for accessing financial data and reporting for financing companies. By implementing this specification, your API will serve as the data source for ReachApp, enabling all ReachSpec features with customizable configurations.
Reach pulls data from your API in two ways: on-demand sync (when a user clicks the sync button in ReachApp, Reach immediately calls your API endpoints to fetch the latest data) and nightly sync (Reach automatically performs scheduled data synchronization during off-hours to keep data current without interfering with customer workflows).
For authentication, OAuth 2.0 is used both for user sign-in and for API requests. Reach sends OAuth 2.0 access tokens in the Authorization: Bearer <token> header with every API request. Your API is responsible for validating these tokens and deciding whether to authenticate the request. Reach does not enforce authentication requirements - that decision is entirely up to your implementation.
Endpoints for OAuth 2.0 authentication and authorization flows. We follow the OAuth 2.0 specification (RFC 6749).
High-Level Authentication Flow:
/oauth2/authorize) where they authenticate and grant access./oauth2/token).expires_in field (in seconds) returned in the token response.Authorization: Bearer <token> header with every API request.Client Credentials: The client ID and client secret provided to Reach are expected to not expire (at least for now).
Endpoints for retrieving basic company information and metadata.
This data helps Reach identify and configure the company within the platform. The fiscal month end is particularly important as it determines how Reach aligns reporting periods and calculates year-to-date figures.
Endpoints for accessing reference data such as chart of accounts, budgets, classes, and departments.
Reference data defines the structure and organization of financial information:
Reach uses this reference data to structure reports and allow customers to filter and slice their financial data.
Endpoints for retrieving non-financial metrics and operational KPIs.
Non-financial metrics are quantitative measures that aren't derived from the general ledger but are useful for business analysis. Examples include:
These metrics can be used alongside financial data in Reach dashboards to calculate ratios (e.g., revenue per employee) or provide operational context.
Endpoints for accessing financial statements including profit and loss, balance sheet, and cash flow statements.
These endpoints return the core financial data that powers Reach's reporting, forecasting, and analysis features:
All endpoints support optional filtering by budget, class, and department to enable segment-level reporting.
curl -i -X GET \
'https://developer.reachreporting.com/_mock/openapi/companies/{CompanyId}/profit-loss?StartDate=2025-01-01&EndDate=2025-01-31&AccountingBasis=CASH&BudgetId=string&ClassId=string&DepartmentId=string' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Successful operation
{ "Data": [ { … }, { … }, { … }, { … } ] }
curl -i -X GET \
'https://developer.reachreporting.com/_mock/openapi/companies/{CompanyId}/cash-flow-statement?StartDate=2025-01-01&EndDate=2025-01-31&BudgetId=string&ClassId=string&DepartmentId=string' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Successful operation
{ "Data": [ { … }, { … }, { … }, { … }, { … } ] }
curl -i -X GET \
'https://developer.reachreporting.com/_mock/openapi/companies/{CompanyId}/balance-sheet?StartDate=2025-01-01&EndDate=2025-01-31&AccountingBasis=CASH&BudgetId=string&ClassId=string&DepartmentId=string' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Successful operation
{ "Data": [ { … }, { … }, { … }, { … }, { … }, { … } ] }