Delete a font
Authorization
ApiKeyAuth API key from Settings → API Keys.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
curl -X DELETE "https://example.com/api/v1/brand_kit/fonts/string"{ "id": "cm4bka8e20001js04xq2v9k3m", "deleted": true}Upload a font POST
Adds a font your templates can use. Send `multipart/form-data` with a `file` part, or JSON with `filename` and `content_base64`. Fonts are **team-level**: once uploaded, every template in the team can name it. Re-uploading the same filename replaces it. The response carries `family` — the name read out of the file itself, and **that exact string is what goes in `fontFamily` on a text component**. It is usually not the filename: `Anton-Regular.ttf` declares the family `Anton`. `.ttf` and `.otf` only, 10MB maximum. A variable font will not register — instance it to a static weight first. A file with no readable family name is rejected, because the renderer would never apply it.
Browse the template library GET
Lists the ready-made templates you can copy into your team. This is the discovery half of copy-then-edit, the path most callers take: find the closest design here, copy it with `POST /api/v1/templates` and `from_library`, then edit the copy like any other template. `fields` is included so you can tell whether a template carries the data you have before copying anything. Read-only. Library templates are curated and promoted by hand; there is no authoring API behind this.