Skip to main content
DELETE
/
fonts
/
{id}
Delete font
curl --request DELETE \
  --url https://api.nexrender.com/api/v2/fonts/{id} \
  --header 'Authorization: Bearer <token>'
This response does not have an example.

​
Why Delete Fonts?

  • Reduce clutter in your font list
  • Avoid confusion from similarly named fonts
  • Clean up test uploads or duplicates
Deleting fonts does not affect jobs that are already rendered. However, future jobs referencing that font may fail if it’s not re-uploaded.

​
Common Mistakes

  • Forgetting the Authorization header
  • Using a deleted or invalid font ID
  • Using GET instead of DELETE

​
Best Practices

  • Always list fonts first before deleting
  • Ensure no active templates or teams rely on the font
  • Rename and re-upload fonts instead of constantly deleting

​
API Reference

Authorizations

​
Authorization
string
header
required

Bearer token authentication using API tokens for team-based access control.

You can generate your own API token at: https://app.nexrender.com/team/settings

Path Parameters

​
id
string
required

Unique font identifier to delete

Response

Font successfully deleted

⌘I