Fonts

The fixed set of built-in font families available on the rendering server — the ones every organisation can reference in a template’s font settings. Use it to populate a font picker in your own UI, or to check a family name before publishing a template that depends on it.

Custom fonts are not in this list

This endpoint returns the built-ins only. Font families your organisation uploaded in the workspace are equally usable in a template but are not listed here, and the Public API has no endpoint that lists them. If your organisation uses custom fonts, a picker built from this endpoint alone will be incomplete.

Endpoint

GET /v1/fonts

Example

Python

import asyncio
from pagr import PagrApiClient

async def main():
    async with PagrApiClient("pagr_prod_xxxxxxxx") as client:
        fonts = await client.get_fonts()          # list[str]
        print(len(fonts), "families")
        for family in fonts:
            print(family)

asyncio.run(main())

TypeScript

import { PagrApiClient } from 'pagr';

const client = new PagrApiClient('pagr_prod_xxxxxxxx');

const fonts = await client.getFonts();            // string[]
console.log(fonts.length, 'families');
for (const family of fonts) console.log(family);

Java

import org.example.PagrApiClient;
import java.util.List;

try (PagrApiClient client = new PagrApiClient("pagr_prod_xxxxxxxx")) {
    List<String> fonts = client.getFonts();
    System.out.println(fonts.size() + " families");
    fonts.forEach(System.out::println);
}

C#

using Pagr.Sdk;

using var client = new PagrApiClient("pagr_prod_xxxxxxxx");

IReadOnlyList<string> fonts = await client.GetFontsAsync();
Console.WriteLine($"{fonts.Count} families");
foreach (var family in fonts)
    Console.WriteLine(family);

Ruby

require "pagr"

client = Pagr::Client.new("pagr_prod_xxxxxxxx")

fonts = client.fonts                              # Array<String>
puts "#{fonts.size} families"
fonts.each { |family| puts family }

C++

#include "pagr/PagrApiClient.hpp"

pagr::PagrApiClient client("pagr_prod_xxxxxxxx");

const auto fonts = client.get_fonts();            // std::vector<std::string>
std::cout << fonts.size() << " families\n";
for (const auto& family : fonts) {
    std::cout << family << "\n";
}

A get_fonts_async form returning std::future<std::vector<std::string>> is also available.

cURL

curl "https://api.pagr.eu/v1/fonts" \
  -H "Authorization: Bearer pagr_prod_xxxxxxxx"

Path parameters

None.

Query parameters

None.

Request body

None — this is a GET.

Response

200 → a plain array of strings, not wrapped in an object:

[
  "Arial", "Courier New", "DejaVu Sans", "DejaVu Sans Mono", "DejaVu Serif",
  "Georgia", "Helvetica", "Inter", "Lato", "Liberation Mono", "Liberation Sans",
  "Liberation Serif", "Merriweather", "Montserrat", "Open Sans",
  "Playfair Display", "Roboto", "Source Code Pro", "Times New Roman", "Verdana"
]

This is the only list endpoint that is not wrapped in the paged envelope — the set is small and fixed, so there is nothing to page.

An unresolvable family fails at render time, not here

Referencing a family that is neither a built-in nor one of your organisation’s live custom families is not an HTTP error. It produces an UnresolvedFont render issue at Warning severity — which means it renders fine on a test key and is blocked on a production key. The same issue is raised when a custom family is found but has no uploaded file for the bold/italic variant the template asks for: the render falls back within the family, and production must not ship that silently. Catch either case early with Validate data.

SDK reference

SDK	Method	Returns
Python	await client.get_fonts()	list[str]
TypeScript	await client.getFonts()	string[]
Java	client.getFonts()	List<String>
C#	await client.GetFontsAsync(cancellationToken)	IReadOnlyList<string>
Ruby	client.fonts	Array<String>
C++	client.get_fonts() / get_fonts_async()	std::vector<std::string>

Errors

This endpoint takes no input, so only auth and transport errors apply — 401 (bad key), 429 (rate limited), 5xx. As a read, the SDKs retry transient server failures automatically. See Errors for the full table.

Related articles

• Validate data — catch an unresolvable font before rendering.
• Errors → Render issues — where UnresolvedFont sits.
• Fonts — the workspace view of font management.