Flinks · FinOps Profile

Flinks Finops

FinOps view of Flinks spend. Flinks bills through sales-quoted enterprise contracts rather than public usage rates. Cost typically accrues per bank connection (Connect), per enrichment or analytics call (Enrich / Score), per payment transaction (Pay), and per processed document (Upload). Because Connect is the primary billable event, cached (MostRecentCached) mode and careful re-authorization reduce redundant institution hits and spend.

Flinks Finops is the FinOps profile for Flinks on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 5 billable meters, billed in CAD, on a monthly cycle, and pricing category committed-use.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Financial Data, Open Banking, Bank Aggregation, Fintech, and Canada.

Category: Financial Data and Analytics Pricing: Committed-Use Billing: Monthly FOCUS v1.3
Financial DataOpen BankingBank AggregationFintechCanadaFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchaseAdjustment

FOCUS Columns

BillingCurrency
CAD
ChargeCategory
Usage
InvoiceIssuerName
Flinks
PricingCategory
Committed-Use
ProviderName
Flinks
PublisherName
Flinks
ServiceCategory
Financial Data and Analytics
ServiceName
Flinks

Meters

connections
Unit: connections
Bank connections established via Connect / Authorize, the primary billable aggregation event.
enrichment_requests
Unit: requests
Enrich attribute and categorization calls (GetAttributes / GetCategorization).
score_requests
Unit: requests
Income and credit-risk analytics calls (GetIncomeAttributes / GetCreditRiskAttributes).
payment_transactions
Unit: transactions
EFT / Interac payment transactions processed via the Pay product.
documents_processed
Unit: documents
Bank statement / transaction documents processed via Upload and FraudAnalysis.

Sources