Sharing, embeds and data

This is an abstract view: how the two doors work, and the shape of what your web team receives. We do not publish a full endpoint catalogue here. The exact line and credentials are issued when we set you up.

Two ways in

• Embedded components — A finished, styled chart or table rendered directly into your page. Your team adds a single line where it should appear; it stays current on its own.
• Structured data — The figures behind a component, delivered as data for your own systems to render however they like.

What is typically available

Growth-of-an-investment (VAMI), performance summaries, fiscal-year and calendar-year return tables, key statistics, and investment exposure over time. In the report library these are marked Client API or REST API. If something you want is not marked, ask — the list grows on request.

Snippets

The markup below is the shape of an embed. Your team receives the exact line, with your domain already registered.

<!-- Issued at setup. Renders only on domains registered to your account. -->
<div data-qr-embed="vami_chart" data-portfolio="YOUR_CODE"></div>

Structured data is the same idea as JSON rather than a finished visual. This is illustrative, not a public schema:

{
  "component": "performance_summary_table",
  "portfolio": "YOUR_CODE",
  "as_at": "2026-06-30",
  "series": [{ "label": "Portfolio", "1y": 0.082, "3y_pa": 0.071 }]
}

A third door — a named REST route for every widget — is not documented here on purpose. If you need a route, we issue it with the component.

Getting set up

Tell us what you want to show and where. We configure the components, register the domains they are permitted to appear on, and give your web team the line to place. Send staging as well as live.

If you are about to commission a website refresh or a client area, raise it first. Deciding what will be embedded before the design is finished is easier than retrofitting it afterwards.