API

Font compliance

• POST https://www.typographystandard.org/api/v1/scan: upload WOFF2, WOFF, TTF, OTF, or ZIP; returns report ID, redirect URL, embed URL
• GET https://www.typographystandard.org/api/v1/report?id={id}: full report JSON with pillars, criteria, and certificate ID
• GET https://www.typographystandard.org/api/v1/verify?id={certificate_or_report_id}: public verification (status, hash, validity)
• GET https://www.typographystandard.org/api/v1/embed?id={id}: embed HTML, iframe snippet, and loader script for score widget
• GET https://www.typographystandard.org/embed/{id}: standalone embed page (iframe-friendly)
• GET https://www.typographystandard.org/api/v1/benchmark: reference library scores

Document evidence

• POST https://www.typographystandard.org/api/v1/audit: upload PDF or image; returns evidence report ID and risk summary

Payments

• POST https://www.typographystandard.org/api/v1/checkout: create Stripe session for verified certificate or evidence report
• POST https://www.typographystandard.org/api/v1/webhook: Stripe webhook (server-side only)

Embed widget

After a scan, use the embed API to retrieve copy-paste HTML matching the Typography Standard score widget used on certified foundry pages: expandable pillars, criterion tooltips, and links to the full report.

<div id="ts-embed-{report_id}" data-ts-report="{report_id}"></div>
<script async src="https://www.typographystandard.org/assets/ts-embed-loader.js" data-ts-report="{report_id}"></script>

Or fetch structured data: GET /api/v1/embed?id={report_id} returns html, iframe_snippet, loader_snippet, and asset URLs.

Automation flow

1. POST font file to /api/v1/scan
2. Store returned id in your CMS or pipeline
3. Poll or webhook on certificate purchase for permanent storage
4. Embed widget via /api/v1/embed on specimen pages

Certificate fees fund registry hosting, audit infrastructure, and standard maintenance.