CompanyCam's API lets you read, create, update, and delete Projects, Photos, and most other CompanyCam data from your own systems. This article covers what the API can do, how to generate keys, and where to go if you want to build an integration for other CompanyCam customers to use.

This feature is only available on the web app.

How the API works

Our API is a REST-based API built to work with your existing tech stack. You can use it to:

Create Projects from your CRM
Sync Photos to your job management software
Subscribe to a webhook when a Photo is tagged
Read and write Pages, Checklists, and Project Groups

You don't need a separate developer account to build with the API. Signing up for CompanyCam creates the same account either way. If you're new to CompanyCam, create a CompanyCam account to start a free 14-day trial. If you already have an account, make sure you're on a paid plan.

Note: Admins and Managers can generate keys and manage Custom Integrations. Standard Users can't generate keys yet.

Applications

An Application is the integration itself — its identity and registration in CompanyCam. It's separate from an Application Key, which is the credential that authorizes access on that Application's behalf. Register an Application once, then create as many Application Keys against it as you need.

If you're planning to publish your integration to the CompanyCam Marketplace, an Application also gives it its own OAuth 2.0 credentials, so any customer can install and authorize it without sharing a personal key.

See Registering an Application for setup steps.

Note: You'll need to register an Application before you can create an Application Key, even for a private integration built just for your own team. Personal Access Tokens don't require this step.

Generating a key

You'll need a key to authenticate your integration. There are 2 types:

Personal Access Token — tied to your User account. Use this for quick, personal scripts or testing.
Application Key — tied to a specific integration, not a person.

When you create a key, you'll also choose a permission tier (Read only, Read & Write, Full access, or Custom) and give it a name so you can identify it later.

Note: Only Admins and Managers can generate a key. Keys and tokens expire, so check the Access Tokens page periodically and generate a new one before an active integration's key expires, or it'll stop working.

See Creating Access Tokens and Application Keys for the exact steps to generate and copy your key.

Publishing an integration for all CompanyCam customers

Building something just for your own company is one path. If you want to build an integration and publish it so any CompanyCam customer can install it, that's a different process, and it's what an Application (above) is for. Check out our guide to partnering with CompanyCam to see what that involves.

Getting started with the docs

All developer documentation now lives in our Developer Portal, including the interactive API reference, a Postman collection, the OpenAPI spec, and a public changelog. This replaces our old docs site.

Note: Our support team can point you to the right documentation, but they aren't developers. Troubleshooting a custom build needs to happen on your end or with your development team. We recommend working with someone who has API experience to make sure everything's set up correctly.

Important: If you're currently building on Using CompanyCam's Legacy API, you have until September 1, 2027, to migrate to this one. After that date, it will no longer work.

Connecting AI to your CompanyCam data

CompanyCam also offers an MCP Server in Beta, which lets you connect AI tools like Claude or Cursor directly to your CompanyCam data. Once connected, you can use plain language to ask about, read, create, and update most data, like Projects and Photos, in CompanyCam.

See Connecting the CompanyCam MCP Server for setup steps.

FAQs

Do I need a developer account for the API?

A developer account isn't required to use the API. Signing up for CompanyCam creates the same account either way.

Can Admins and Managers generate a key?

Admins and Managers can generate keys and set up Custom Integrations.

Can Standard Users generate a key?

Standard Users can't generate keys yet.

How do Personal Access Tokens differ from Application Keys?

Personal Access Tokens are tied to your account and work well for personal use. Application Keys are tied to the integration itself and work better for anything shared with a team.

What's the difference between an Application Key and an Application?

An Application Key authenticates a private integration built for your own team. An Application is a separate OAuth 2.0 credential used by third-party developers building an integration for the CompanyCam Marketplace. See Registering an Application for setup steps.

What happens to my existing integration built on Using CompanyCam's Legacy API?

Integrations built on Using CompanyCam's Legacy API will keep working until September 1, 2027. After that date, migrating to this API is required to keep them running.

Can I publish my integration for other companies?

Publishing an integration for all CompanyCam customers is a different path from building one for your own company. Check out our guide to partnering with CompanyCam for the public route.

Will CompanyCam support help troubleshoot my build?

CompanyCam support can point you to the right documentation and resources, but we aren't developers. Troubleshooting a custom integration happens on your end or with your development team.

💡 Need more help?

Contact our Support team — we're here Monday through Friday.

The CompanyCam Community has real job-site examples, templates, and tips from crews using this every day. Jump in with a question or just browse.

Building Custom Integrations with CompanyCam's API