TenantPoint API Keys for Zapier
Create, scope, rotate, and revoke a dedicated TenantPoint API key for a Zapier connection.
#Create a dedicated key
An Owner or Admin can create keys in Settings → Developers → API keys. Create a separate key for each Zapier connection. TenantPoint shows a newly created raw key once; save it directly in Zapier's protected connection field because it cannot be retrieved later.
The complete initial Zapier catalog requires properties:read, vendors:write, work_orders:write, and webhooks:write. A resource's write scope includes read access for that same resource only. Do not grant unrelated permissions merely to work around a setup error.
#Protect and replace keys
TenantPoint stores API keys as hashes. The selected environment, API origin, key prefix, and webhook configuration must agree; TenantPoint rejects a mixed-environment connection.
If a key may have been exposed, its Zap owner leaves, or access is no longer needed, revoke it and create a replacement. Update the Zapier connection with the replacement. Never reuse another person's key or share a key with TenantPoint support.