Use a fixed endpoint when your system already knows the company and the data it needs. Retrieve available historical company financials with the reporting period, currency, account scope and source context kept beside the figures.
Built for server-side integration. Token authentication and product entitlement required.
GET /v2/kyb/29707645/financial
?include_provenance=true
{
"years": ["2022-01-31", "2023-01-31"],
"groups": [{
"name": "Summary",
"list": [
{ "name": "Currency", "list": {
"2023-01-31": "GBP"
}},
{ "name": "Total Assets", "list": {
"2023-01-31": "45327.0"
}}
]
}],
"source": { "name": "…", "url": "…" }
}Example response shape · abridged
The deterministic API moves financial records into your application without adding a generated interpretation layer.
Retrieve the available statement fields, ratios and company financial indicators in a machine-readable response organised by reporting date.
Use the returned years and groups rather than assuming every company has the same fields.Resolve the legal entity once, retain its company ID and call the financial endpoint whenever your workflow needs the underlying data.
Veripoint retrieves the dataset through GET /kyb/{id}/financial.Keep currency, reporting period, consolidated-account scope and optional provenance with every value you ingest or display.
A missing or null field is unavailable data. It is not zero.The AI API is not a newer version of the deterministic API. They solve different engineering problems and can sit in the same architecture.
Your application chooses the financial endpoint and receives the structured records.
View the financial data APIThe service resolves the entity, selects the tools and streams the result.
View the AI research API| Decision | Deterministic Financial API | AI Financial Research API |
|---|---|---|
| Best starting point | Known company and known dataset | A self-contained business question |
| Execution | Your code calls one explicit endpoint | The service selects and can chain data tools |
| Transport | A structured JSON response | A live Server-Sent Events stream |
| Output | Financial fields, periods and ratios | ai: answer plus data · data: tool results only |
| Consistency | Fixed route and response contract; source records can update | Retrieved facts remain source-backed; tool path and prose can vary by question |
| Best workload | ETL, models, dashboards, scheduled retrieval | Research assistants, investigations, unfamiliar questions |
| Main trade-off | Your team defines the workflow and interpretation | More flexible input, but more streaming and review logic |
Simple rule: use deterministic endpoints for repeatable system workloads; use the AI API when a person or agent starts with a question whose retrieval path is not known in advance.
The integration stays explicit at every stage. Your application controls entity matching, storage, calculations and presentation.
If you do not already have the Global Database company ID, search by legal name, country, registration number, VAT number or another supported identifier. Confirm the entity before using its figures.
Request GET /v2/kyb/{id}/financial for the company dataset used by Veripoint. The Financials API also documents direct company-ID and ticker routes.
Read the years array and the returned groups. Preserve the reporting date, currency and individual or consolidated account scope when normalising the response.
Add include_provenance=true when source metadata is required. Version the retrieved payload so later calculations can be reproduced against the same record.
Populate models with reported values and ratios without extracting figures from a generated narrative.
Best when formulas and mappings are already defined.Ingest company financial data into scheduled pipelines, internal dashboards and downstream scoring systems.
Best when schema control, caching and repeatability matter.Display financial statements or derived metrics inside your product, subject to the agreed usage and redistribution rights.
Best when your application owns the presentation and analysis.Keep routine ingestion, calculations and dashboards on deterministic endpoints. Use the AI Financial Research API for open-ended questions, ambiguous entities and requests that need several data tools. This protects schema control without forcing users to understand the endpoint catalogue.
See the AI research layerThe product choice affects transport, validation, cost controls and the evidence you need to retain.
Direct answers for product, data and engineering review.
A financial data API lets software request company financial records in a machine-readable format. This product returns available company financial fields and statement groups for use in models, dashboards, applications and data pipelines.
Your application chooses the endpoint, company and parameters, and receives the endpoint’s defined response shape without generated commentary. Deterministic does not mean the source record is frozen; values can change when new filings or corrections become available.
After resolving the company, Veripoint pulls the dataset through GET /v2/kyb/{id}/financial. The wider Financials API also documents company-ID and ticker-based routes.
Financials API is the product family for structured company financial data. Financial KYB is the entity-resolved route Veripoint uses to return years and statement groups for a known company ID, with optional provenance.
It returns the financial fields available for that company and reporting period, organised into the groups provided by the source response. Availability varies by jurisdiction, company type, filing obligations and source coverage, so integrations must handle partial statements.
The product is designed for company financial data across private and public companies where records are available. The exact fields, history and freshness depend on disclosure rules and the available source filings.
Yes. Supported KYB requests accept include_provenance=true. Preserve the returned source metadata with the figures when auditability or downstream evidence is required.
Keep null or absent values as unavailable. Do not convert them to zero or silently estimate them. Your application can show another relevant returned metric, but it should not relabel a different field as the missing one.
It is the better fit when the entity and required dataset are already known and your system needs a predictable schema. Confirm contracted limits and throughput before finalising a batch or scheduled architecture.
Use the AI API when the input is an open-ended question, the company still needs to be resolved, or the task may require several data tools. Use the deterministic API when your application already knows the route and needs structured values at scale.
Tell us the companies, volume, output and usage rights your product requires.