Register a custom font on a site and get a presigned S3 URL to upload the font binary.
The response includes a customFont object and an upload object. Use the upload.url and upload.fields
to POST the font binary directly to S3 as multipart/form-data. The binary must go in a field named file
and must be the last field in the form (an AWS S3 requirement). S3 returns 201 Created on a successful upload.
To learn more, see Custom fonts.
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)
The CSS font-family name (1-256 characters). Commas are stripped server-side.
CSS font-weight value (1-1000)
CSS font-display value
Font registered. 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.