Api pricing bg 1
Transparent API Pricing

Simple, predictable API pricing — based on real usage

You pay only for the data you request.
No subscriptions, no per-user fees, no bundled features.

FinImpulse API pricing is designed for developers and data teams building real products — from MVPs to production systems. Costs are calculated per request and per data row returned, with full transparency and linear scaling.

Transparent pricing structure

How FinImpulse API pricing works

Each API request has a base call cost

Every request includes a small per-call charge that covers request processing, normalization, and delivery

Some endpoints return multiple data rows

When an endpoint returns lists or historical records, a lightweight per-row cost applies based on the actual data returned

You only pay for what you receive

No minimum volumes. No bundled features. Optimized responses, filtering, and caching help reduce unnecessary usage

Pricing by data category

Instead of pricing per product or per user, pricing is based on the type and volume of data returned

Data Category Typical Use Cases Pricing Model
Search & Discovery Global asset search, ticker lookup, autocomplete Per call + Result rows
Market Snapshots Summary, profile, ownership overviews Per call
Historical Data Prices, returns, valuation history Per call + Data rows
Fundamentals Financial statements, valuation metrics Per call + Data rows
Statistics & Risk Ratios, performance, volatility, risk indicators Per call
News & Events News, filings, press releases Per call + Article rows

Usage-based pricing, designed for predictable growth

Pricing is based exclusively on API usage, which includes the number of requests made and the amount of data returned.

There are:

  • no per-user fees
  • no feature bundles
  • no artificial tiers

You pay only for the data you consume.

How usage typically scales

As products grow, usage usually increases along three dimensions:

More assets

Larger universes, portfolios, or coverage

More data depth

Historical records, statistics, fundamentals

More frequent refresh cycles

Intra-day updates, automation

Pricing scales linearly across all dimensions — without step functions or surprises.

How pricing works

Request-level pricing examples

These examples illustrate how individual API requests are priced. Actual cost depends on response size and data returned.

Historical price data

/history Hybrid (call + rows)

Every request includes a small per-call charge that covers request processing, normalization, and delivery

Call cost
$0.00015
per request
Data rows
$0.00003
per row returned
Price 1

Company or fund profile

/profile Per call

Used to retrieve descriptive, non-tabular data such as company or fund overview, classification, and metadata.

Call cost
$0.00040
per request
Price 2

Financial statements

/financials?type=income_statement Hybrid (call + rows)

Typically returns multi-year financial statement data, where cost depends on the number of reporting periods included.

Call cost
$0.00080
per request
Data rows
$0.00020
per row returned
Price 3

Why this pricing model works

  • Costs are transparent at the request level
  • You can estimate usage before building
  • Scaling is linear and predictable

For the complete list of endpoints and detailed pricing rules, see the API documentation.

Ready to explore?

Need exact numbers for your use case?

Explore full pricing details in your dashboard or test the API with $1 free credit.

Background Circle Background Circle