Does Opagio offer API access for programmatic valuations?

Short Answer

Yes — Opagio Public API v1 is a read-oriented REST API on the Scale, Growth Fund and Multi-Fund plans. It returns valuations and company records you already hold; it does not compute valuations.

Full Explanation

Opagio Public API v1 is a REST API for organisations that need Opagio data inside their own systems — a board pack assembled each quarter, an internal data warehouse, a lender reporting template, or an investor update. It is deliberately read-oriented, and being precise about that is more useful than a long feature list: the API returns valuations and company records your organisation already holds, and it does not run calculations on demand. Availability is a plan-level feature rather than a separate contract: API access is enabled on the Scale, Growth Fund and Multi-Fund plans. Keys are issued inside Opagio Intangibles under Settings → API keys by a user holding the API key-management permission; they are not created through the API itself. A key is the prefix opagio_pk_ followed by 64 hexadecimal characters, 74 characters in total, and it is shown once at creation — only a SHA-256 hash and a short display prefix are stored, so a lost key must be revoked and reissued rather than recovered. Each key carries four scopes: read:valuations, read:portfolio, read:webhooks and write:webhooks. The read surface covers valuation reports as a list and individually, a portfolio KPI summary with sector breakdown, company records, and a small summary payload for an embeddable widget. Every request is bound to the single organisation that owns the key, so cross-tenant reads are not possible, and a resource owned by another organisation returns 404 rather than 403 so that its existence is never disclosed. The only writes on the surface are outbound webhook subscriptions: you register an HTTPS URL against a list of event names and verify each delivery with an HMAC-SHA256 signature. Two rate-limit ceilings apply to every call and both must pass — 300 requests per 15 minutes per source IP, and 300 requests per 15 minutes per API key — so spreading one key's traffic across many addresses buys no additional throughput. Several capabilities are often assumed and do not exist today: there is no endpoint that accepts financial data and returns a computed valuation, no bulk write path for portfolio or company data, no benchmarking or questionnaire endpoint, no sandbox environment, and no published OpenAPI schema or client SDKs. Any HTTP client will do. The developer guide linked below documents authentication, the scopes, pagination and the response envelope in full.

Try It Yourself

intangibles guides intangible-asset-valuation-api

Related Questions

How does Opagio's AI Valuator work?

Opagio's AI Valuator uses financial inputs, industry benchmarks, and proprietary algorithms to estimate the fair value of intangible assets across mul...

What methodology does the Opagio Calculator use?

The Opagio Calculator uses a multi-factor model that combines financial metrics, industry benchmarks, and the CHS intangible asset framework to estima...

How does the Opagio Questionnaire scoring work?

The Opagio Questionnaire scores intangible assets across the six CHS categories using weighted responses, producing a 0-100 score per category and an ...

Want to see these concepts in action?

Take the free intangible asset assessment to see how these concepts apply to your business.