How to enable the Dash API for Medialake, add your Dash credentials to Medialake as an access key, and what happens when you sign in to connect.
What to expect
Dash is connected through OAuth 2.0 with your organization's own Dash API credentials. Setup has two parts:
A one-time setup by administrators. A Dash admin turns on the Dash API, which issues a Client ID and Secret key, and adds Medialake's callback URL to the allowed list. A Medialake administrator then saves the Client ID, Secret key, and your Dash subdomain as an access key.
Signing in to connect. Whoever connects Dash in Medialake is sent to Dash's own sign-in page at
login.dash.app, signs in, and is returned to Medialake. Medialake never sees or stores your Dash password. The Dash API supports only this sign-in flow, so a person signs in once for each connection.
We follow the principle of least privilege. The Dash connector only reads content: it lists your Dash folders, searches the assets in the folders you select, reads their file details and previews, and downloads the files it syncs. It does not upload, edit, tag, move, or delete anything in Dash.
Dash administrator Medialake Dash
│ enable API, add │ │
│ callback URL │ │
│──────────────────────────────────────────────────▶│
│ │ │
Medialake administrator
│ save access key │ │
│────────────────────────▶│ │
│ │ │
Team member
│ connect source │ │
│────────────────────────▶│ │
│ redirect to Dash │ │
│◀────────────────────────│ │
│ sign in to Dash │ │
│──────────────────────────────────────────────────▶│
│ redirect with code │ │
│◀──────────────────────────────────────────────────│
│ │ exchange code │
│ │────────────────────────▶│
│ │ access + refresh │
│ │ token │
│ │◀────────────────────────│
│ choose folders │ │
│────────────────────────▶│ │
│ │ read-only requests │
│ │────────────────────────▶│
Before you begin
You will need:
A Dash admin account, to turn on the Dash API and manage its callback URLs. If you are not an admin, ask one to do Step 1 for you.
Your Dash subdomain: the first part of your Dash address. For
https://yourcompany.dash.app, the subdomain isyourcompany.Administrator privileges in Medialake, to save the access key.
A Dash account for the person who will connect Dash in Medialake. Medialake works with the access of the Dash user who signs in, so use an account that can see the folders you want to sync.
>Keep the credentials private. Treat the Secret key like a password. 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 values you enter encrypted and never shows them again.
Step 1: Enable the Dash API and add Medialake's callback URL
Log in to Dash as an admin.
Go to Admin → Integrations and open the REST API tab.
Turn on Enable API. Dash shows your Client ID and Secret key.
Add Medialake's callback URL to the allowed callback URLs:
https://yourcompany.medialakeapp.com/dash-redirect
Replace yourcompany.medialakeapp.com with the address you use to sign in to Medialake. Enter it exactly, including https:// and with no trailing slash.
Copy the Client ID and Secret key.
Turning Enable API off revokes the Client ID, Secret key, and saved callback URLs, and turning it back on issues a new Client ID and Secret key. Any integration that uses the old values, including Medialake, stops working until it is updated.
Step 2: Add the credentials to Medialake
You need administrator privileges in Medialake for this step.
In Medialake, open Administration → Integrations from the sidebar.
Open the Dash integration.
In the Access Keys section, click Create New Setting.
In the New access key panel, enter a Name for the key, for example
Marketing Dash app. The name is shown in the access key list and next to every account that connects with it.Under Credentials, fill in each field:
| Field | What to enter |
| --- | --- |
| Enter your Dash Client ID here without any space | The Client ID from Step 1. |
| Enter your Dash Client Secret here without any space | The Secret key from Step 1. |
| Enter your Dash subdomain (e.g. my-account from my-account.dash.app) | Your subdomain only, for example yourcompany. Do not enter https:// or .dash.app. |
Under Who can use it?, choose the teams that can connect Dash with this key, or make it available to all teams.
Click Save access key.
Medialake checks the format of each value before saving: the Client ID must be 8 to 128 letters, numbers, periods, underscores, or hyphens; the Secret key must be 16 to 256 characters with no spaces; and the subdomain may contain only letters, numbers, and hyphens.
Connect Dash and choose what to sync
With the access key saved, any team member who is allowed to connect sources, on a team that can use the key, can add Dash:
Open Connections → Catalogue from the side menu.
Find Dash and click Connect.
Under Access key, select the key saved in Step 2.
Optionally click Test. For Dash, this checks the Client ID and Secret key with Dash's sign-in service; the subdomain and callback URL are checked when you connect.
Click Connect. Medialake sends you to Dash's sign-in page.
Sign in with your Dash account. Dash returns you to Medialake.
Nothing is synced automatically. Your Dash folders appear as folders in Medialake: open a folder to see its subfolders, and select the folders Medialake should sync. Selecting a folder syncs the assets in it and in all of its subfolders. Assets that are not in any Dash folder cannot be selected.
For each asset, Medialake syncs its current file and skips file types it does not support. A new Dash source syncs automatically once a week by default; you can change this to daily or monthly.
The permissions we request
Scope | Why Medialake requests it |
| Lets Dash issue a refresh token, so Medialake can keep the connection working without asking you to sign in again. |
| Tells Dash which Dash account the connection is for. Medialake fills in the subdomain from the access key. |
Limiting what Medialake can access
Medialake acts with the access of the Dash user who signs in, so that user's permissions in Dash are the strongest control. For the narrowest connection, sign in with a Dash account that can see only the folders you want to sync. A non-admin user with Dash's Basic access to those folders covers what the connector does: Basic lets a user view and download assets, but not upload, edit, or delete them. Dash admins can see and download every asset in every folder.
The folders you select in Medialake control what is synced, but they do not narrow what the signed-in account could reach.
What Medialake can and cannot do
With the configuration above, Medialake can:
Read the signed-in Dash user's name, email address, and profile picture, to identify the connection
Read your Dash folder settings and list your folders
Search the assets in the folders you select
Read file details such as names, sizes, media types, and dates added, and retrieve previews and thumbnails
Download the content of the assets it syncs
Medialake does not:
See your Dash password
Upload, replace, edit, tag, move, or delete assets
Create or change folders, fields, or metadata
Manage Dash users, integrations, or account settings
Staying connected
Dash access tokens expire. When Dash rejects an expired token, Medialake uses the refresh token, together with the stored Client ID and Secret key, to get a new access token and retries the request. No sign-in or user action is needed.
The connection stops working, and the source is marked unauthorized in Medialake, if Dash refuses the refresh — for example because Enable API was turned off and on again, which issues a new Client ID and Secret key. To restore it, save a new access key with the current credentials and connect again.
Revoking access
To revoke Medialake's access from Dash, turn off Enable API on the REST API tab under Admin → Integrations. This revokes the Client ID, Secret key, and saved callback URLs, so it also affects any other integration that uses them.
In Medialake, an administrator can also delete the access key from the Dash integration's Access Keys section. Remove the Dash source in Medialake as well if it should no longer sync.
Troubleshooting
Symptom | What to check |
A "format is invalid" message for the subdomain field when saving | Enter only the subdomain, for example |
A "format is invalid" message for the Client ID or Client Secret field when saving | Paste the values again, checking for spaces picked up when copying. |
"A setting with this title already exists in the group. Choose a different title." | Another Dash access key already uses that name. Choose a different Name. |
Test reports "The provider rejected these credentials." | Check the Client ID and Secret key. If Enable API was turned off and on again since they were copied, Dash issued new values. |
Test reports "These credentials look right, but the provider couldn't confirm them just now." | Dash did not give a definite answer. Try connecting; the credentials are checked again when you do. |
Dash shows a callback URL error when you connect | The callback URL in Dash must match |
You are returned to the Catalogue with an error after signing in | Medialake could not exchange the sign-in for a token. Check the Client ID, Secret key, and callback URL, then connect again. |
Connecting ends on an Incorrect Credentials. page | Medialake could not read your Dash user details after sign-in. Check that the subdomain in the access key matches the Dash account you signed in to. |
"This connection link is invalid or has expired. Please start the connection again." | The sign-in took too long or the link was reused. Start again from Connections → Catalogue. |
"No integration settings available for this service." when connecting | No Dash access key is available to your team. Ask a Medialake administrator to save one, or to add your team under Who can use it? |
An expected folder is missing | The Dash user who signed in cannot see it. Connect with an account that has access to the folder. |
Some assets are not synced | Assets that are not in any Dash folder cannot be selected, and assets with unsupported file types are skipped. |
If the issue continues, contact [email protected] with your Dash subdomain, the access key's name, and the error message. Do not include the Secret key.
Further reading
Using the Dash API — turning on the REST API and adding callback URLs
Dash API documentation — the OAuth sign-in flow, scopes, and the folder and asset endpoints used by the connector
Questions about connecting Dash? Contact [email protected].
