For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Resources
Get started
ReferenceGuidesExamplesChangelog
ReferenceGuidesExamplesChangelog
  • Data API
    • Introduction
  • Token
    • GETGet Authorization User Info
    • GETGet Authorization Info
  • Sites
    • GETList Sites
    • GETGet Site
    • GETGet Custom Domains
    • POSTPublish Site
  • Pages and Components
  • CMS
  • Forms
  • Custom Code
  • Assets
  • Custom fonts
      • GETList custom fonts
      • GETGet custom font
      • POSTCreate custom font
      • PATCHUpdate custom font
      • PUTReplace custom font file
      • DELDelete custom font
      • POSTBatch delete custom fonts
  • Comments
    • GETList Comment Threads
    • GETGet Comment Thread
    • GETList Comment Replies
  • Ecommerce
  • Webhooks
    • GETList Webhooks
    • GETGet Webhook
    • POSTCreate Webhook
    • DELRemove Webhook
  • Site Configuration
  • Enterprise
LogoLogo
Resources
Get started
Custom fontsCustom fonts

Batch delete custom fonts

POST
https://api.webflow.com/v2/sites/:site_id/custom_fonts/batchDelete
POST
/v2/sites/:site_id/custom_fonts/batchDelete
$curl -X POST https://api.webflow.com/v2/sites/580e63e98c9a982ac9b8b741/custom_fonts/batchDelete \
> -H "Authorization: Bearer <token>" \
> -H "Content-Type: application/json" \
> -d '{
> "items": [
> {
> "id": "66f3a1b2c4d5e6f7a8b9c0d1"
> }
> ]
>}'
1{
2 "deleted": [
3 {
4 "id": "66f3a1b2c4d5e6f7a8b9c0d1"
5 }
6 ],
7 "failed": [
8 {
9 "id": "00000000000000000000abcd",
10 "name": "NotFound",
11 "msg": "Font not found"
12 }
13 ]
14}
Delete 1-100 custom fonts in a single request. The response is always `200 OK` for a valid request body. Per-font results are reported in the `deleted` and `failed` arrays. The endpoint is idempotent: fonts that do not exist appear in `failed` with `name: "NotFound"` rather than failing the entire request. You can safely retry a partial failure by re-sending only the IDs that did not appear in `deleted`. Required scope | `sites:write`
Was this page helpful?
Previous

List Comment Threads

Next
Built with

Delete 1-100 custom fonts in a single request. The response is always 200 OK for a valid request body. Per-font results are reported in the deleted and failed arrays.

The endpoint is idempotent: fonts that do not exist appear in failed with name: "NotFound" rather than failing the entire request. You can safely retry a partial failure by re-sending only the IDs that did not appear in deleted.

Required scope | sites:write

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

site_idstringRequiredformat: "objectid"
Unique identifier for a Site

Request

Request body for bulk-deleting custom fonts

itemslist of objectsRequired

Response

Request was successful. Check deleted and failed arrays for per-item results.

deletedlist of objects
failedlist of objects

Errors

400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
404
Not Found Error
429
Too Many Requests Error
500
Internal Server Error