Before today, if you wanted to use Adobe Fonts on your Webflow project, you’d need to add your API kit to your account integration settings. Then, for the specific project, you’d choose a font kit from your account to be applied for that site.
But this approach was annoying for those of you wanting to use Adobe Fonts on multiple client projects, requiring you to manage client’s fonts under your own account, and deal with time consuming handoffs if the client goes somewhere else. (Adobe will also begin requiring clients to have their own Adobe accounts starting in 2020).
Today’s update makes things simpler: now your clients can set up their own free Adobe Font accounts, then send you their API key for placement in the project settings of their own site. That way, they get to keep control of their fonts, without you needing to manage those fonts within your own account.
Now you can set Adobe Font (formerly Typekit) API keys on a per-project level. This means your clients can set up their own free Adobe Font accounts, then hand you the API key for use on their project.