Skip to main content
There are two ways to manage users and accounts with Captain Data:
  1. Platform Access — Manage workflows via our user-friendly Platform UI.
  2. API Access — Directly manage your users and accounts through our API.

​
Platform Users

Designed for GTM teams (growth, sales, and marketing) that want to build and manage workflows directly through Captain Data’s Platform UI.
User Roles & Permissions:
  • Owner - Full platform access with permissions to manage users, accounts, billing, and subscriptions. Best for project managers or workspace administrators.
  • User - Basic platform access but no rights to manage billing or subscriptions. Best for team members like marketing or sales staff.
  • External User - No access to the Captain Data platform. Can only connect accounts via shared links. Best for External SaaS users or Clients.

​
API Customers

As described in the article Adding & Managing Users, you can use Captain Data’s API to manage your SaaS users directly. This approach provides flexibility, scalability, and white-label capabilities. Reminders for API Usage Modes:
  • Your company’s branding takes center stage, but Captain Data powers everything behind the scenes.
  • Example: Companies like Zeliq use their own Chrome extension and branding while leveraging Captain Data as the backend. Users see Zeliq’s branding instead of Captain Data.
Ideal for: Companies that want a fully branded, customer-facing experience with complete Captain Data support in the background.
  • Rent LinkedIn accounts without using a Chrome extension.
  • Use Captain Data as an API or data provider while we manage the accounts for you.
Ideal for: Companies that want a “behind-the-scenes” integration with zero visibility to end users.
  • A hybrid model where users interact with Captain Data’s Chrome extension, which remains branded as “Captain Data.
  • Often utilizes the Shared Account feature, enabling users to send access links for easy account connection.
Ideal for: Companies that want some level of control but don’t mind limited Captain Data branding visibility.

​
Accounts Management FAQ

No, it is not required to pass the li_a cookie in the request body.We automatically generate the li_a cookie during the last update based on the li_at value.However, if the user has multiple subscriptions (e.g., Sales Navigator and Recruiter), providing the li_a cookie is preferred. It can make the API call faster as it is tied to the session.
Related Article: Adding & Managing Users
Captain Data respects LinkedIn’s limits and uses Smart Limits to avoid exceeding the daily number of visits. Currently, LinkedIn allows 50-80 profile visits per day.
Related Article: Smart Limits - how to avoid getting warned on social accounts
If the cookies are invalid, it’s likely because the user has either logged out and logged back in (generating new cookies), or the cookies have expired. If LinkedIn disconnects you, make sure the user logs in again to both LinkedIn and Sales Navigator to generate new cookies.While a job is running or when launching a job, the system will return an error message and pause your job.Solutions:
  1. Wait for the extension to refresh the cookies automatically (every 2 hours).
  2. Manually update the cookies by performing a POST request to Add or Update Integration Account. For this, you will need the new li_at and li_a cookies (preferably from Sales Navigator).
Related Article: Retry a Run
Captain Data refreshes cookies for LinkedIn accounts every 2 hours to ensure the session remains active and avoid invalid cookies.If you’re using your own Chrome Extension (white label), you should build a similar mechanism to maintain session activity.
Related Article: Building Chrome Extensions for LinkedIn & Source Code
Yes absolutely! We handle creating “rented” accounts that are completely bundled. You just need to contact us or click on “Add bundled account” on the LinkedIn integration.
Related Article: When to Sync Identities vs. Use Rented LinkedIn Accounts

​
Troubleshooting

We recommend you to:
  • Check if the parameters (e.g., country, shared_account, etc.) are set correctly.
  • When updating an account, only update the fields you want to change.
    Implement retries when updating an account and ensure timeouts are appropriately set.
    Related Articles: Adding & Managing Users as well as Errors & Retries Mechanism