Skip to content

Suggested searches

    Search all documentation ↑↓ to navigate Enter to open Esc to close

    Deepgram

    Connect Deepgram as an access review source using a project API key with Owner or Admin scope so Probo can list every project's members.

    Markdown

    Probo reads your Deepgram account’s members through the Deepgram Management API so you can review who has access.

    • Probo organization administrator access
    • The Owner or Admin role in Deepgram (the key must carry owner or admin scopes so it can enumerate every project and its members)
    • A key created under a project where its holder has the Owner or Admin role, so the key can see all projects across the account
    Probo fieldDeepgram fieldNotes
    NamenameFirst and last name, falling back to the email
    EmailemailThe member’s email address
    RolescopesAn owner scope maps to Owner, an admin scope maps to Admin, otherwise Member
    AdminscopesFlagged as an administrator when the member holds an owner or admin scope
    StatusNot supported
    MFANot supported
    Last loginNot supported
    External IDmember_idStable identifier used to track the account across reviews
    Created atNot supported

    Creating a new API key in the Deepgram Console

    1. In the Deepgram Console, open the Projects dropdown (top left), select the project, then go to Settings > API Keys.
    2. Click Create a New API Key, name it (e.g. Probo Access Review), and choose the Owner or Admin role so the key carries members-read access across the account. You can optionally set an expiration.
    3. Copy the key and store it securely. It’s shown only once.
    1. In Probo, go to Settings > Connectors and click Add more to open the Marketplace.
    2. Find Deepgram and open it.
    3. Enter a Name for the connection (e.g. main), paste the key into API key, and click Connect.
    4. Go to Access Review > Sources, click Add sources, tick Deepgram, and click Add.

    Probo names the source Deepgram. An account may span several projects, so the source keeps its generic name rather than a specific organization or project name.

    • Key rejected. Confirm it’s a Deepgram project API Key with the Owner or Admin role, sent under the Token scheme. Short-lived Bearer access tokens from the token-based Auth API won’t work.
    • No members appear. The key must carry owner or admin scopes so it can enumerate every project and its members. A Member-role or narrowly scoped project key that cannot see all projects is insufficient.