CompanyCam's open API and developer documentation make it easy to build a custom integration, whether it's just for your team or for other CompanyCam customers to use. This article covers what's available, where to start, and who on your team can set it up.

Important: This article covers using CompanyCam's Legacy API, which is only available on the web app. Support ends September 1, 2027, after which it will no longer work. Migrate to Building Custom Integrations with CompanyCam's API to keep your integration running.

Open API overview

If you want to build a custom integration for your own team, get started with our developer documentation today.

If you want to build an integration that's available to all CompanyCam customers, check out our guide to partnering with CompanyCam.

Note: Admins can build and manage custom integrations. If you don't have that role, ask an Admin on your account to set it up. Our support team can point you to the right documentation, but we recommend working with a developer, or someone experienced with APIs, to build and troubleshoot your integration.

Developer accounts

Getting started is simple: you just need a CompanyCam account. Already have one? A separate developer account is optional, though you're welcome to sign up here if you'd prefer to keep things separate.

Core API

The Core API is where you work with core CompanyCam data. You can read, create, update, and delete most CompanyCam entities, like Projects and Photos. It's built as a REST API, so it's straightforward to integrate into most solutions.

Some ways teams use the Core API:

Creating Projects from a CRM
Syncing Photos to job management software
Subscribing to a webhook when a Photo is tagged

Get started today.

Key features

OAuth 2.0

CompanyCam uses the OAuth 2.0 authorization code grant type. This issues both an access token and a refresh token, and works through your users' browser rather than a direct server-to-server connection.

Webhooks

Webhooks let your integration subscribe to CompanyCam events as they happen, instead of repeatedly checking the API for updates. When an event matches your webhook's scope, we send a POST request to your webhook URL in real time.

Looking for a ready-made connection instead of building your own? Browse our full list of integrations.

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.

FAQs

Do I need a developer account for the API?

A developer account is optional if you already have a CompanyCam account. You can create a separate one through our developer signup page if you'd rather keep development separate from your main account.

Can Standard Users build custom integrations?

Standard Users cannot build custom integrations. Only Admins can build and manage them. Ask an Admin on your account for help if you need one set up.

What can I do with the Core API?

The Core API lets you read, create, update, and delete CompanyCam data such as Projects and Photos. Teams commonly use it to:

Create Projects from a CRM
Sync Photos to job management software
Trigger a webhook when a Photo is tagged

How do webhooks work in Using CompanyCam's Legacy API?

Webhooks send a POST request to your webhook URL whenever a subscribed event happens, so your integration gets real-time updates without repeatedly checking the API. This is how webhooks work here; new integrations should use Building Custom Integrations with CompanyCam's API.

Do I need to register an Application before creating an Application Key?

You'll need to register an Application before creating an Application Key. An Application Key is always tied to a registered Application. See Registering an Application for setup steps.

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

An Application is the integration's identity and registration. An Application Key is the credential, tied to that Application, that actually authorizes access.

Is Using CompanyCam's Legacy API still recommended for new integrations?

Using CompanyCam's Legacy API is not recommended for new integrations. New integrations should be built on Building Custom Integrations with CompanyCam's API instead.

What happens to my integration after Using CompanyCam's Legacy API is retired?

Integrations built on Using CompanyCam's Legacy API will stop working once it's retired on September 1, 2027. Migrating to Building Custom Integrations with CompanyCam's API before that date avoids disruption.

Can I publish my integration for all CompanyCam customers?

Publishing an integration for all CompanyCam customers is possible through our partner program.

Will CompanyCam support help troubleshoot my integration?

CompanyCam support can point you to the right documentation and resources, but 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.