Replace the binary of an existing custom font while preserving its ID and any references to it. The upload handshake is identical to Create custom font.
If the existing font has a non-empty axes array (a variable font), you must include an axes field
in the request. Send axes: [] to declare that the new binary is a static font, or send the new variable
axes to declare it is still variable. Omitting axes when the existing font is variable returns 400.
Required scope | sites:write
Bearer authentication of the form Bearer <token>, where token is your auth token.
File name including extension. Accepted extensions are .woff2, .woff, .ttf, .otf, and .eot. Maximum 256 characters.
Lowercase hex MD5 hash of the font binary (exactly 32 characters)
Variable font axes for the replacement binary. Required when the existing font has a non-empty axes array.
File replacement initiated. Upload the binary to the presigned S3 URL in upload to complete the process.
Presigned S3 upload details. Post the font binary to url as multipart/form-data, including every key from fields plus the binary itself in a field named file. The file field must be the last field in the form.