How do I generate a PDF or HTML factsheet from an ISIN?

One call

bash
curl -s -X POST https://fundfactsapi.com/api/v1/factsheets \
  -H "Authorization: Bearer $FUNDFACTS_API_KEY" -H "Content-Type: application/json" \
  -d '{"isin":"IE00B4L5Y983","format":"pdf","title":"Prepared for J. Doe","accent":"#1F5EFF","theme":"light"}' \
  -o factsheet.pdf

The response is the document (application/pdf or text/html); the headers X-Factsheet-Url and X-Factsheet-Pdf-Url carry keyless links to the same render.

Links instead of bytes

bash
curl -s -X POST https://fundfactsapi.com/api/v1/factsheets -H "Authorization: Bearer $FUNDFACTS_API_KEY" -H "Content-Type: application/json" \
  -d '{"isin":"IE00B4L5Y983","format":"html","deliver":"link"}'

json
{ "id": "fs_…", "isin": "IE00B4L5Y983", "name": "iShares Core MSCI World UCITS ETF", "format": "html", "dataAsOf": "2026-09-01",
  "urls": { "html": "https://fundfactsapi.com/f/…", "pdf": "https://fundfactsapi.com/f/….pdf", "embed": "<iframe src=\"https://fundfactsapi.com/f/…\" title=\"Fund factsheet\" width=\"100%\" height=\"1100\"></iframe>" } }

The URLs need no key: mail the PDF link to a client, put the HTML link in a CRM, paste the embed snippet in your page. GET /factsheets lists your renders, GET /factsheets/{id}?format=pdf re-renders, PATCH marks favourites, DELETE removes.

Options

No code

The dashboard's Factsheets tab (https://fundfactsapi.com/dashboard?tab=factsheets, free account) makes the same sheet without code: search the fund by name or paste its ISIN, pick PDF or web page, the theme, an accent colour and the name in the header, then generate. Every public fund page under /funds/{isin} has a button that opens the generator on that fund.

In your own layout

The factsheet is rendered with the open-source React components in @fundfactsapi/widgets (growth chart, donut, weight bars, key-fact tiles, risk scale, returns tables and a composite FundFactsheet), so you can also build the page yourself from the JSON and print it with your own stack. Generate PDF factsheets from JSON and the client reporting use case show both routes.