How to create a read-only Frontify developer token, add it to Medialake with your Frontify domain, and understand exactly what access it grants.
What to expect
Frontify is connected with a developer token and your Frontify domain. There is no Frontify sign-in or consent screen when you connect: a Medialake administrator saves the token and domain once as an access key, and Medialake authenticates to your Frontify instance in the background from then on. Medialake does not use an OAuth client ID and client secret for Frontify; the developer token is the only credential it accepts.
A Frontify developer token belongs to the user who created it. It can reach everything that user can access, limited further by the scopes chosen when the token was created. We follow the principle of least privilege: the recommended setup is a dedicated service user, invited only to the brands and libraries you want to sync, with a token that has only the basic:read scope.
The Frontify connector only reads content. It lists your brands and libraries, reads image and video asset details, retrieves thumbnails, and downloads the assets you select. It does not upload, edit, tag, move, or delete anything in Frontify.
Frontify developer tokens always expire, so plan to replace the token before its expiry date (see Staying connected).
Administrators Medialake Frontify
│ create a basic:read │ │
│ developer token for a │ │
│ dedicated service user │ │
│───────────────────────────────────────────────────────▶│
│ save token + domain │ │
│ as an access key │ │
│───────────────────────────▶│ │
│ │ │
Team member │ │
│ connect with the key │ identify the token's │
│ │ user on your domain │
│───────────────────────────▶│──────────────────────────▶│
│ choose brands and │ read-only requests │
│ libraries │ │
│───────────────────────────▶│──────────────────────────▶│
Before you begin
You will need:
Your Frontify domain: the address you use to open Frontify in your browser, for example
yourcompany.frontify.comor a custom domain such asbrand.yourcompany.comA Frontify user for the integration, ideally a dedicated service user (see Step 1), and the ability to sign in as that user
Help from a Frontify administrator to invite that user to the right brands and libraries
Administrator privileges in Medialake, to save the access key
>Keep the token private. Frontify shows a developer token only once, and its support team cannot recover a lost one. Store it in an approved password manager or secret-management system. Do not email it, paste it into a support ticket, or commit it to source control. Medialake stores the token encrypted and never shows it again after you save it.
Step 1: Create a dedicated service user in Frontify
A developer token has access to everything its user can access, so Frontify recommends creating tokens for integrations under a dedicated service user rather than a personal account.
Create an email address for the integration, for example
[email protected], and invite it to Frontify.Complete the sign-up for that user. Frontify suggests starting the user's name with "DO NOT DELETE" so nobody removes the account by mistake.
Invite the user only to the brands and libraries Medialake should sync, with permissions that let it view and download their assets.
Step 2: Create a developer token
Sign in to Frontify as the service user from Step 1.
Go to
https://yourcompany.frontify.com/oauth-access-token, replacingyourcompany.frontify.comwith your own Frontify domain.Click Create Token.
Give the token a name and description that say where it is used, for example
Medialake sync.Select only the
basic:readscope. Medialake only reads from Frontify, so leave every write scope unselected. Scopes cannot be changed after the token is created.Choose an expiration period. Pick the longest period your security policy allows, and record the expiry date somewhere your team will see it.
Click Create, then copy the token immediately. You cannot view it again after the dialog closes.
Step 3: Add the token to Medialake
You need administrator privileges in Medialake for this step.
Open Administration → Integrations from the sidebar.
Open the Frontify integration.
In the Access Keys section, click Create New Setting.
In the New access key panel, enter a Name that identifies the token, for example
Frontify service user. Including the token's expiry month in the name makes rotation easier to track. The name is shown in the access key list and next to every account that connects with it.Under Credentials, fill in:
- Frontify Developer Token: the token from Step 2.
- Frontify Tenant: your Frontify domain only, without https:// and without a trailing slash.
Under Who can use it?, choose the teams whose members can connect Frontify with this key, or make it available to all teams.
Click Save access key.
The Frontify Tenant must be the full domain, because Medialake sends every request to https:///graphql. For example:
yourcompany.frontify.com
Medialake checks both fields when you save. The token must be 16 to 128 characters long and contain only letters, numbers, dots, underscores, and hyphens. The tenant must be a domain name made of letters, numbers, dots, and hyphens.
An access key cannot be edited after it is saved. To change the token or domain later, save a new access key and connect with it, as described under Staying connected below.
Step 4: Connect Frontify and choose what to sync
Any team member who is allowed to connect sources can do this, as long as the access key is available to their team.
Open Connections → Catalogue from the side menu.
Find Frontify and click Connect.
Under Access key, select the key you saved in Step 3.
Optionally, click Test to check the token with Frontify before connecting.
Click Connect.
There is no Frontify login screen. Medialake asks your Frontify domain which user the token belongs to and adds the account under that user's name.
Next, choose what to sync. Your Frontify brands appear as folders, and you can open a brand to see its libraries. Select a whole brand to sync the libraries in it, or open the brand and select individual libraries. Medialake syncs the image and video assets in your selection; other asset types, and files whose type Medialake does not support, are skipped. Nothing outside your selection is imported.
Limiting what Medialake can access
Two layers control what the connection can reach, and Frontify enforces both:
The service user's permissions. The token can only access the brands and libraries its user can access. Inviting the service user to as little as possible is the strongest control.
The token's scopes. With only
basic:read, even a leaked token could not change or delete anything in Frontify.
Selecting brands and libraries in Medialake controls what is synced, but it does not narrow the token itself. Review the service user's access periodically.
What Medialake can and cannot do
With the setup above, Medialake can:
Identify the user the token belongs to (name and email address)
List the brands and libraries that user can access
Read image and video asset details such as titles, descriptions, file names, sizes, dates, authors, tags, copyright and license information, and the library and folder each asset sits in
Read video details such as dimensions, duration, and bitrate
Retrieve thumbnails
Download the assets in the brands and libraries you select
Medialake cannot:
See any Frontify user's password
Access brands, libraries, or assets the service user cannot access
Upload, replace, edit, tag, move, or delete assets, because the token has only the
basic:readscopeManage Frontify users, brands, or settings
Staying connected
Medialake sends the saved token with every request. It does not refresh or extend Frontify tokens.
Every Frontify developer token expires at the end of the period chosen in Step 2. When it expires, Frontify stops accepting it, the account stops syncing, and it shows a Service Disconnected warning in Medialake. To avoid an interruption, replace the token before it expires:
Create a new token for the same service user (Step 2).
Save it as a new access key with the same Frontify domain (Step 3).
Connect again with the new access key (Step 4). Connecting the same Frontify user on the same domain in the same team updates the existing account instead of adding a second one.
Once no account uses the old access key, delete it from the integration's Access Keys section.
Do not rely on a reminder from Frontify; keep track of the expiry date yourself. If the account was disconnected for a reason that has since been fixed on the Frontify side, for example the service user's access was restored, click Check connection on the warning to test the saved token again.
Revoking access
To stop Medialake from reaching Frontify:
In Frontify: revoke the developer token, or remove the service user's access to the brands and libraries. The token can never reach more than its user can.
In Medialake: remove the Frontify account if it should no longer sync. Once no account uses the access key, delete it from the integration's Access Keys section. Medialake will not delete an access key that a connected account still uses.
Troubleshooting
Symptom | What to check |
"The Frontify Tenant format is invalid." when saving | Enter the domain only, for example |
"The Frontify Developer Token format is invalid." when saving | Paste the whole token with no spaces before, after, or inside it. |
"A setting with this title already exists in the group. Choose a different title." when saving | Another Frontify access key already uses that Name. Choose a different name. |
Test reports "The provider rejected these credentials." | The token is wrong, has expired, or was revoked. Create a new token and save it as a new access key. |
Test reports "These credentials look right, but the provider couldn't confirm them just now." | Medialake could not get an answer from your Frontify domain. Check that the Frontify Tenant is spelled correctly and opens Frontify in your browser. If it does, Frontify may be temporarily unavailable; try again in a few minutes. |
An Incorrect Credentials. page appears after clicking Connect | Medialake could not identify the token's user on your Frontify domain. Run Test on the access key, and check both the token and the domain. |
A brand or library you expected is not listed | The service user has not been invited to it. Grant access in Frontify, then open the sync selection again. |
A library syncs, but some assets do not appear | Medialake syncs image and video assets only, and skips file types it does not support. |
The account shows Service Disconnected after working normally | The token has most likely expired. Follow the steps under Staying connected. |
If the issue continues, contact [email protected] with your Frontify domain, the name of the access key, and the error message. Do not include the token.
Further reading
Creating a developer or service user token — Frontify's guide to developer tokens, scopes, expiry, and service users
What is the Frontify GraphQL API? — overview of the API the connector uses
Frontify Developer Portal — the full API reference, including the list of scopes
Questions about connecting Frontify? Contact [email protected].
