Talvrin

Resources · Documentation

Connect trusted market research to your workflows.

Controlled, permission-aware access to Talvrin evidence and research outputs — scoped by contract, entitlement, market and data rights. Availability depends on where each capability sits in our release process, shown exactly as it stands below.

No live endpoint, sandbox credential, SDK or webhook delivery exists yet. This page documents the governance, security and evidence model this capability must meet before any of that ships.

Research and intelligence platform. No trade execution. No manufactured investment recommendations.

Smiling analyst with glasses seated in a bright office

What you will be able to connect

Four capability groups, each scoped and rights-checked before a single response leaves Talvrin.

The external API is a scoped product capability, not a general-purpose feed. Every capability below declares its release status, outputs, and licensing limits before it can ship.

Evidence & Provenance

In specification

Claims, sources, validation status, versions and corrections — read-only, rights-filtered access to the same evidence record the product shows.

Research Workflows

In specification

Approved research jobs and their results, with eligibility verified before any response returns.

Entitlements & Rights

In specification

Licensed usage boundaries — export, display and redistribution rules enforced per data class, independent of connection success.

How access works

Review contract → Obtain access → Test → Go live.

The same four-step architecture pattern applies regardless of which capability you request — no shortcuts around contract review or eligibility.

  1. 01

    Review contract

    Read the versioned interface spec, errors, types and semantics before requesting anything.

  2. 02

    Obtain access

    Scoped credentials issued under least privilege, tied to tenant, role and approved jurisdictions.

  3. 03

    Test

    Validate against documented, schema-checked examples in a controlled environment.

  4. 04

    Go live

    Only after every applicable publication gate records a named approval.

Release governance

One capability registry decides what's real — navigation never invents status.

Every capability moves through the same five states. Product, Engineering and Compliance share one authoritative record; nothing here is published ahead of it.

  1. Not approved

    Default state — internal specification only. No public nav, teaser or endpoint.

    Current state

  2. Internal build

    Private documentation and test credentials inside protected environments only.

  3. Limited pilot

    Invite-only access for approved tenants under specific pilot terms.

  4. Public release

    Overview, reference and console available according to entitlement.

Ten gates must pass before any capability can claim “live.”

  • G01

    Contract

    Approved interface spec — versioning, errors, types, retries.

  • G02

    Rights

    Written entitlement and licensing evaluation per data class.

  • G03

    Security

    Threat model, tenant isolation and penetration-test sign-off.

  • G04

    Source fidelity

    Provenance, source versions and correction handling verified.

  • G05

    Operations

    Rate limits, monitoring, revocation and incident ownership.

  • G06

    Documentation

    Accurate reference, examples, limitations and support process.

  • G07

    Commercial

    Packaging, terms, pricing path and sales readiness approved.

  • G08

    Privacy / region

    Data-protection assessment and jurisdiction routing reviewed.

  • G09

    Accessibility

    WCAG 2.2 AA public UI and error states tested.

  • G10

    Release

    Named Product, Engineering, Security and Legal sign-off recorded.

Integration patterns

Deliberately narrower than a generic market-data terminal.

Each pattern requires its own source-rights analysis and a maintained contract before it can be requested. None of the patterns below are released interfaces today.

Query evidence

Authorized retrieval of evidence metadata and permitted source-linked observations.

Rights-aware filtering — never bypasses fact validation or coverage.

Retrieve approved research

Read released structured research artifacts or job output.

Same source restrictions and fact lineage as the first-party product.

Start a research job

Asynchronous job contract for expensive, documented workloads.

Idempotency, quotas, completion state and tenant policy enforced.

File / batch exports

A scoped evidence bundle or report, only where contract and source terms expressly allow.

Export rights, retention and traceability checked before release.

SSO / enterprise identity

Separate identity integration — not evidence-data API access.

Contract-approved enterprise SSO and configured tenant policy.

Receive events

Optional signed webhooks for released workflow or monitoring events.

Approval-gated signed delivery with retries — never implied as currently live.

Evidence & rights

What must survive every API boundary.

The API does not convert restricted documents into freely distributable facts. Rights and evidence states are enforced server-side before any response leaves Talvrin — never inferred from a technically successful request.

May

Return evidence with its source registry identity, jurisdiction, licence terms and freshness rule attached.

Must never

Convert a restricted document into a freely distributable fact.

May

Expose validation states such as verified, derived-verified, conflicting, stale or unsupported.

Must never

Flatten those states into a single confident numeric answer.

May

Evaluate retrieve, store, cache, index, AI-use, display, export and redistribution permissions independently.

Must never

Let a technically successful request bypass the rights engine.

May

Expose supersession, correction and version history where approved.

Must never

Silently overwrite a historical view when a source is revised.

May

Deny a request and log the reason when rights or policy prohibit output.

Must never

Return a “derived data” substitute to route around a restriction.

Developer documentation — preview

Documentation will answer what's supported, what a request means, and what can fail — before any integration code is written.

Illustrative — shown for structure, not yet published
Professional in glasses listening during a meeting

*Webhooks only appear in documentation once the capability is operationally supported. OpenAPI 3.1.1 is the preferred publication format; every example is schema-validated and marked synthetic unless taken from cleared, reproducible test fixtures.

A representative evidence object

Synthetic example

GET /v1/evidence/{evidence_id}  [PROPOSED EXAMPLE — NOT A LIVE ENDPOINT]

{
  "id": "ev_example_001",
  "observation": { "metric": "illustrative_metric", "value": null,
                   "unit": "unit_example", "status": "VERIFIED_SOURCE" },
  "source": { "publisher": "example_originator",
              "source_document_id": "doc_example_001",
              "locator": "section_example", "version": "v1" },
  "time": { "valid_at": "2026-01-01T00:00:00Z",
            "published_at": "2026-01-02T00:00:00Z",
            "recorded_at": "2026-01-03T00:00:00Z" },
  "methodology": { "type": "reported", "version": null },
  "usage_rights": { "display": false, "export": false,
                    "redistribute": false },
  "coverage": { "scope": "example", "limitations": [] }
}
  • 403 ENTITLEMENT_DENIED
  • 451 RIGHTS_OR_POLICY_RESTRICTED*
  • 409 SOURCE_CONFLICT
  • 422 UNSUPPORTED_SCOPE*

Security & operations

Security and reliability are part of the product promise, not hidden infrastructure.

These are minimum design references for the eventual external perimeter — not claims that a certification or audit has already been obtained.

Authentication

OAuth 2.0 authorization-code + PKCE for user-delegated access; short-lived tokens bound to audience, client and scope.

Object authorization

Every evidence, job and tenant object read or export is tested against broken object-level authorization.

Transport & network

TLS everywhere, a strict CORS allow-list, and SSRF defenses on any callback destination.

Error safety

Stable, non-secret reason codes; sensitive failures never leak credentials or internal detail.

Replay & webhook safety

Signed events, TTLs, clock-skew checks and idempotent replay prevention where webhooks are released.

Rate & resource use

Per-tenant and per-client quotas, bounded pagination and backoff — no denial of service via unbounded jobs.

Design references: OpenAPI Specification 3.1.1 · OAuth Security BCP (IETF RFC 9700) · OWASP API Security Top 10 (2023) · WCAG 2.2 AA — implementation references, not certification claims.

Answer-first FAQ

Frequently asked, answered first.

No. This page describes the governance model and intended capability shape for Talvrin’s external API and integrations. No live endpoint, sandbox credential, SDK or webhook delivery exists yet — availability will be stated here only once it is genuinely released.

Nothing to connect yet — but the access model is exact.

Start with Developer Overview to see the current developer resource state, or tell us about your intended workflow so we can evaluate fit before anything ships.

Research and intelligence platform. No trade execution. No manufactured investment recommendations.