Understanding the Purpose of Clay API Keys in Workspaces

·Sep 21, 2025 04:06 AM·

What exactly is the use of "Clay API Key" which are generated team-member-wise? Why does looking up into a table need an API key when its WITHIN the same workspace. Also, why should it be tied to a team member? If that person is removed from the workspace, then ALL their lookup tables get broken immediately.

2 comments

· Sorted by Oldest

Hunain F.
·
·
A Clay API key is tied to each team member for security usage tracking and accountability If that member is removed their key becomes invalid and lookups break the solution is to create a dedicated service account and use its API key so everything stays stable
Siddhant B.
·
·
@Clay Team - please note that when we remove someone's Clay API key, not only do their corresponding Lookup table enrichments stop working instantly, but the details WITHIN the enrichments also get DELETED!

Hunain F.
·
·
A Clay API key is tied to each team member for security usage tracking and accountability If that member is removed their key becomes invalid and lookups break the solution is to create a dedicated service account and use its API key so everything stays stable
Siddhant B.
·
·
@Clay Team - please note that when we remove someone's Clay API key, not only do their corresponding Lookup table enrichments stop working instantly, but the details WITHIN the enrichments also get DELETED!