CompanyCam API: Keys, Tokens, Webhooks, and the Legacy Shutdown
Facts checked November 2026 against CompanyCam's help center and developer documentation.
The short answer
Yes. CompanyCam has a public REST API that reads, creates, updates, and deletes projects, photos, and most other CompanyCam data. You need a paid plan, an Admin or Manager creates the keys, and setup happens in the web app only. New integrations go on the Public API in CompanyCam's Developer Portal; the older API stops working in September 2027. Source: Building Custom Integrations with CompanyCam's API, CompanyCam Help Center, read November 2026.
Who can create a key, and on which plan
CompanyCam's API article tells existing accounts to be on a paid plan and new ones to start the 14-day trial. The token article says the feature is on select plans without naming them, and Plans Explained has no line for the API. Admins and Managers create keys. The token article adds that a Standard User can create a Personal Access Token once an Admin turns that setting on, while the API article still says Standard Users can't generate keys yet. Sources: Building Custom Integrations with CompanyCam's API, Creating Access Tokens and Application Keys and CompanyCam Plans Explained, CompanyCam Help Center, read November 2026.
Create a Personal Access Token
Open Access Tokens
In the web app, click Integrations in the left-hand nav, then Access Tokens.
Start a new token
Click New Personal Access Token. For an Application Key, click New Application Key instead and pick a registered Application.
Set level and expiration
Name it, choose a permission level (Read only, Read & Write, Full access, or Custom) and set when it expires.
Create and copy
Click Create token, then copy the token. Treat it like a password and revoke it if it leaks.
How keys and tokens work
A Personal Access Token acts as the person who made it. An Application Key acts as a registered Application, which an Admin or Manager sets up first under Integrations > Applications. No credential can do more than the account that created it. Keys expire after 7, 30, 60, or 90 days, or never, with 30 as the default; an expired key stops working, and an Application Key also stops when the user who created it is deactivated. Sources: Creating Access Tokens and Application Keys and Registering an Application, CompanyCam Help Center, read November 2026.
Webhooks, OAuth, and rate limits
The Public API lives at api.companycam.com/public_api/v1. Apps that act for other CompanyCam customers sign them in with the OAuth 2.0 authorization code grant and granular scopes. A webhook calls your server the moment a project, photo, or other record changes, and each call carries an X-CompanyCam-Signature header you can check. CompanyCam documents its request limits for the API and the MCP server on the Rate Limits page of its Developer Portal; read the current figures there. Sources: CompanyCam Developer Portal and CompanyCam Public API spec, CompanyCam developer documentation, read November 2026.
Zapier, if you would rather not write code
CompanyCam also connects through Zapier, where CompanyCam can be the trigger, such as a new photo or project, or the action. Only an Admin can connect the account, setup happens in a web browser, and no data moves until a Zap you built is on. Source: Connecting and Using CompanyCam with Zapier, CompanyCam Help Center, read November 2026.
The legacy API ends September 2027
CompanyCam's help center says the legacy API stops working in September 2027. The legacy API is the /v2 API, so an integration built on /v2 has to move to public_api/v1 before then. The Developer Portal says the /v2 API stays supported until September 2027, and the old docs site's banner says it will be deprecated in early 2027. Sources: Using CompanyCam's Legacy API, CompanyCam Help Center; CompanyCam Developer Portal, CompanyCam developer documentation; Welcome (legacy API docs), docs.companycam.com; all read November 2026.
LibreCam: the API and MCP come with every account
MCP and API on every account
The built-in MCP server and the API come with every account, the free plan included, with no seat and no add-on.
Reads and writes what you can
Call the API from your own tools, or connect Claude or ChatGPT. Either one reads and writes whatever the signed-in user can.
No per-user pricing
Add the office, a sub, or a new hire, and the price does not move.
If you are thinking of moving
Start with an export: download your CompanyCam photos. Then bring the project folders into LibreCam, and run both apps side by side for two weeks before you cancel anything.
Related CompanyCam guides
Also read: CompanyCam + Zapier, the CompanyCam MCP server, CompanyCam AI and credits, what you can take out of CompanyCam, and CompanyCam pricing. Every guide is on the CompanyCam guides page.
Frequently Asked Questions
Yes. It has a public REST API for projects, photos, pages, checklists, and most other data, documented in its Developer Portal. You need a paid plan, and keys are created in the web app.
In the web app, go to Integrations > Access Tokens, click New Personal Access Token, and follow the steps above. Admins and Managers can do this.
CompanyCam says the API needs a paid plan and names no specific plan; Plans Explained has no API line. The old developer docs still name Pro, Premium, and Elite, CompanyCam's plan names before July 2026.
In September 2027, according to CompanyCam's help center. Integrations built on it stop working after that date unless they move to the current API.
CompanyCam publishes them on the Rate Limits page of its Developer Portal. That page sets the limits for both the API and the MCP server; check the current figures there.