Developers

FinanceGPT API documentation

Build with governed company finance, financial data, investments, quantitative models, QLMs, workflows and MCP through API v2.

OpenAPI YAMLML service
CatalogAPI docsSDKsML serviceAPI plans

Getting started

API v2 is workspace-scoped. Production and sandbox credentials are separate.
Authorization: Bearer <FinanceGPT API key or OAuth service token>
Scopes are explicit. Requests are denied when a credential does not carry the required product scope. Sandbox calls return deterministic fixtures and do not read production workspace data.

Company Finance

Deterministic statements, ratios, resilience assessment, DCF and scenario analysis.
API v2
MethodEndpointScopePurpose
GET/api/v2/companiesfinancial:analysis:readList company finance workspaces
GET/api/v2/companies/{company}/financialsfinancial:analysis:readNormalized financial periods and provenance
GET/api/v2/companies/{company}/ratiosfinancial:analysis:readDeterministic ratios
GET/api/v2/companies/{company}/analysisfinancial:analysis:readRatios, resilience, DCF and linked forecast
POST/api/v2/companies/{company}/valuationsfinancial:analysis:runRun explicit-assumption DCF
POST/api/v2/companies/{company}/scenariosfinancial:analysis:runRun deterministic scenario analysis
curl -H "Authorization: Bearer $FINANCEGPT_API_KEY" \ https://financegpt.tools/api/v2/companies/123/analysis

Investment Clients & Portfolios

Client relationships, portfolio holdings and governed portfolio operations in the FinanceGPT application.
Product surface

FinanceGPT separates recorded portfolio holdings from governed market-data evidence. Client and portfolio screens remain manager-scoped; trading is not implied by holding records. API exposure of personally identifiable client relationship records remains restricted until workspace-scoped client APIs are separately governed.

Recorded holdingsGoverned price evidenceFinancial plansPortfolio constructionScenario analysisExecution controls

Financial Data

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

Planning

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

Investment Intelligence

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

Investment Execution

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

Quant Models

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

Quant Compute

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

ML

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

QLMs

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

Workflows

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

Financial Actions

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.

MCP

Canonical endpoint definitions, required scopes and request schemas are maintained in the OpenAPI specification.
Open specification

Use the OpenAPI document as the machine-readable contract. FinanceGPT keeps production execution and data-access boundaries scope-gated rather than implied by documentation.