Social Profiles

Reminder: All queries on this page require the WORKSPACE-ID header. See Getting Started for setup.

A Social Profile represents a single social media account on a specific platform — one Instagram handle, one TikTok account, one YouTube channel. Each Creator can have multiple social profiles linked to them across different platforms.

Via the API, you can look up a social profile by handle and platform to retrieve follower count, verification status, contact info, and other platform data. This is the same data you see in the Social Profiles page  in the Archive UI.

Terminology note: Some API error messages use the term “influencer” — this refers to the same concept as Social Profile.

Social Profiles vs. Creators

Learn more: Difference Between Creators and Social Profiles 

To look up a creator’s full CRM data, see the Creators page.

All Social Profile fields

Search by handle

query GetSocialProfile {
  socialProfile(accountName: "lauramendez", provider: INSTAGRAM) {
    id
    accountName
    fullName
    provider
    followers
    following
    verified
    proAccount
    private
    avatar
    originalUrl
    email
    phoneNumbers
  }
}

Example response:

{
  "data": {
    "socialProfile": {
      "id": "4829301",
      "accountName": "lauramendez",
      "fullName": "Laura Méndez",
      "provider": "INSTAGRAM",
      "followers": 312000,
      "following": 840,
      "verified": false,
      "proAccount": true,
      "private": false,
      "avatar": "https://cdn.archive.com/avatars/lauramendez.jpg",
      "originalUrl": "https://instagram.com/lauramendez",
      "email": "contact@lauramendez.com",
      "phoneNumbers": []
    }
  }
}

The same query works on every supported platform — just swap the provider value. For example, looking up a YouTube channel:

query GetYouTubeProfile {
  socialProfile(accountName: "Archive_dotcom", provider: YOUTUBE) {
    id
    accountName
    fullName
    followers
    verified
    originalUrl
  }
}

Handle format:

• Pass the handle without the @ prefix (e.g. "Archive_dotcom", not "@Archive_dotcom"). With the @, the cached lookup fails — you’d need fallback: true to recover.
• Lookups are case-insensitive: "archive_dotcom" and "Archive_dotcom" both work and return the same profile.
• YouTube channels are matched by handle, not by channel ID or vanity URL.

Using with AI:

“Search for the Instagram profile of @lauramendez” “Look up the YouTube channel Archive_dotcom” “What’s the follower count for this creator on TikTok?” “Check if this account is verified and whether it’s a business account” “Is @lauramendez a business account on Instagram?”

Search by platform

To get all social profiles for a specific platform, query creators and filter by socialProfiles.provider:

query CreatorInstagramProfiles {
  creators(first: 20) {
    nodes {
      id
      customAttributes
      socialProfiles {
        accountName
        provider
        followers
        verified
      }
    }
  }
}

Then filter client-side (or ask Claude) to show only Instagram or TikTok profiles.

Using with AI:

“Show me all Instagram handles for my creators” “List all creators who have a TikTok account” “Find creators who are on both Instagram and YouTube”

Search with fresh platform data

By default, the socialProfile query only looks within Archive’s local cache — the data already stored in your workspace. This means:

• If the profile is archived in your workspace → returns the cached data
• If the profile is not archived → returns an error: "Social profile not archived. Use fallback: true to fetch from instagram."

When you add fallback: true, Archive fetches the data directly from the platform (Instagram, TikTok, or YouTube) in real time, bypassing the cache. This means:

• You can look up any public profile — not just ones in your workspace
• You get the most up-to-date data from the platform at the time of the query
• The WORKSPACE-ID header is still required even with fallback: true

query SocialProfileWithFallback {
  socialProfile(accountName: "lauramendez", provider: INSTAGRAM, fallback: true) {
    id
    accountName
    fullName
    followers
    following
    verified
    proAccount
  }
}

When to use it:

• Looking up a creator’s profile before adding them to your workspace
• Verifying a handle exists on a specific platform
• Getting the most current follower count for a profile

Using with AI:

“Look up the Instagram profile for @cristiano” “Check if @newcreator exists on TikTok and show me their follower count” “Get the latest data for @lauramendez on Instagram”

Get social profiles via the creators query

Social profiles are also available as a nested field when querying creators. This is useful when you want both CRM data and platform stats in a single request:

query CreatorsWithProfiles {
  creators(first: 20) {
    nodes {
      id
      customAttributes
      socialProfiles {
        id
        accountName
        fullName
        provider
        followers
        verified
        proAccount
        email
      }
    }
    pageInfo { hasNextPage endCursor }
  }
}

Using with AI:

“Show me all creators with their Instagram handles and follower counts” “Get every creator’s email and their linked social profiles”

List all social profiles in the workspace

The socialProfiles connection query pages through every social profile archived in the workspace — useful for exports, audits, or enriching an external CRM without going creator-by-creator:

query ListSocialProfiles {
  socialProfiles(first: 50) {
    totalCount
    nodes {
      id
      accountName
      provider
      fullName
      followers
      verified
      proAccount
    }
    pageInfo { hasNextPage endCursor }
  }
}

Example response:

{
  "data": {
    "socialProfiles": {
      "totalCount": 97,
      "nodes": [
        {
          "id": "43647166",
          "accountName": "lauramendez",
          "provider": "INSTAGRAM",
          "fullName": "Laura Méndez",
          "followers": 312000,
          "verified": true,
          "proAccount": true
        }
      ],
      "pageInfo": { "hasNextPage": true, "endCursor": "..." }
    }
  }
}

Standard cursor pagination applies (max 100 per page).

Note: the query accepts a presetId argument, but as of 2026-07-13 the preset’s filters are not applied to the results — you get the full profile list back regardless. Until that’s fixed, don’t rely on presetId here; page through the full list and filter client-side.

Using with AI:

“Export every social profile in my workspace with handle, platform, and follower count” “How many social profiles are archived in this workspace?”

Social Profile Views

Social Profile Views are the saved filters under Social Listening → Social Profiles Views in the sidebar — e.g. “Mega Influencers” (1M+ followers, verified). The API can list, create, edit, and delete them.

List Social Profile Views

query ListSocialProfileViews {
  socialProfileViews {
    id
    name
    filters
    sort
    showReportingStats
    group { id name }
  }
}

Example response:

{
  "data": {
    "socialProfileViews": [
      {
        "id": "b6c7d8e9-f0a1-2345-bcde-456789012345",
        "name": "Mega Influencers",
        "filters": { "followersCount": { "from": 1000000, "to": null }, "verified": [true] },
        "sort": [{ "field": "followers_count", "direction": "desc" }],
        "showReportingStats": true,
        "group": null
      }
    ]
  }
}

Using with AI:

“List my Social Profile Views and their filters”

Create a Social Profile View

mutation CreateProfileView {
  createSocialProfileView(input: {
    name: "Verified 50k+"
    filters: { followersCount: { from: 50000 }, verified: [true] }
  }) {
    socialProfileView { id name filters }
    userErrors { field message }
  }
}

Both name and filters are required. The view appears in the Archive UI sidebar immediately.

Using with AI:

“Create a Social Profile View for verified accounts with more than 50,000 followers”

Update a Social Profile View

Partial updates are supported — omitted fields keep their current values, so renaming a view doesn’t require re-sending its filters:

mutation RenameProfileView {
  updateSocialProfileView(
    id: "b6c7d8e9-f0a1-2345-bcde-456789012345"
    input: { name: "Verified 50k+ (Q3)" }
  ) {
    socialProfileView { id name filters }
    userErrors { field message }
  }
}

Using with AI:

“Rename my ‘Micro Influencers’ view and raise its follower floor to 25,000”

Delete a Social Profile View

mutation DeleteProfileView {
  deleteSocialProfileView(id: "b6c7d8e9-f0a1-2345-bcde-456789012345") {
    __typename
  }
}

Deleting a view never touches the profiles themselves — it only removes the saved filter. The payload carries no success field; the absence of errors is the success signal.

Using with AI:

“Delete my ‘Old Outreach List’ Social Profile View”