CompanyCam API Guide for Contractors

One-line verdict: The most completely documented photo-platform API in this directory — full read/write on projects and photos — with one paid-plan gate and one deadline your builder needs to respect. Openness: 4 / 5 — rated 4 because CompanyCam documents a REST API with OAuth sign-in, scoped keys, a webhook catalog, and published rate limits, held back from 5 only because API access requires a paid plan.

The connection that works

Rung 1 — Direct connection. CompanyCam’s help center states it plainly: the API “lets you read, create, update, and delete Projects, Photos, and most other CompanyCam data from your own systems.” No separate developer account is needed — your normal CompanyCam account is the developer account. There are two credential patterns, both documented: OAuth 2.0 for apps other companies install (with read / write / destroy scopes), and Application Keys for your own company’s connection, where you pick the permission tier at creation — Read only, Read & Write, Full access, or Custom. That tier picker is exactly the scoped-key discipline this directory recommends.

The core objects are verified at the endpoint level in the vendor’s reference: Projects (create, with address; assign or remove users), Photos (upload a photo to a project, add photo comments, delete), plus documents, users, checklists, comments, and groups. Webhooks are documented with a real event catalog — project.created, photo.created, photo.tag_added, comment.created, document.created, todo_list.completed, and more, with signed payloads and automatic retries. Rate limits are published too: 240 reads a minute, 100 writes a minute (from the legacy documentation — see the deadline below).

The deadline: CompanyCam runs two documentation generations at once. The vendor states the legacy API docs describe an API deprecating in early 2027 and directs builders to the new Developer Portal. The rate limits and webhook catalog above are verified from the legacy docs; the new portal confirms the reference, OpenAPI spec, and Postman collection exist, but its endpoint pages weren’t text-verifiable in our pass — so new-portal specifics are flagged where they matter.

Bridge apps: CompanyCam has a genuine Zapier app — triggers like New Project, New Photo, Photo Tagged, and Checklist Completed; actions like Add Project and Add Photo — documented in CompanyCam’s own guide. No native Make app was found.

Can automate

• Photo flow into the job system — a photo uploaded on site can fire a webhook the moment it lands, so your job system, your client update, or your inspector packet builds itself while the crew is still on the ladder.
• Project creation everywhere at once — when a job is created in your CRM or field-service platform, the matching CompanyCam project can be created automatically, with the crew assigned.
• Documents and checklists — project documents can be uploaded and checklists created from templates through the API, so paperwork follows the job instead of chasing it.
• Scoped access for vendors — partners sign in with OAuth; your own tools get a key tiered to exactly what they need, revocable without touching anything else.

Can’t automate

• Estimates, invoices, or payments through the API — UNVERIFIED. CompanyCam sells proposals, invoicing, and payment processing as product features, but no estimates, invoices, or payments endpoints are documented in the vendor API sources we checked. Product features are not API access.
• A CRM contacts sync — UNVERIFIED. No contacts API object is documented; CompanyCam is a photo system, not your customer database.
• Building on the legacy docs past early 2027 — the vendor has dated them. New builds belong on the new Developer Portal, and the legacy rate limits and webhook catalog should be re-verified there before being treated as current.
• API access on a free plan — the vendor is explicit: API and integrations access comes with paid plans.

Hidden gate: The API only turns on with a paid plan — and the old API docs retire in early 2027, so your builder has to build on the new developer portal, not the old one. A quote that doesn’t mention the migration is a quote that hasn’t read the docs.

Build fit — what this platform supports well

• Job documentation pipelines — the strongest fit in this directory: photos, documents, and checklists move the moment they exist.
• Speed-to-Lead — indirect: CompanyCam isn’t a lead system, but a new project created from your lead tool starts the photo record from minute one.
• Client proof and updates — photo events can trigger client-facing progress updates without office staff re-sending pictures by hand.
• Review Engine — like every platform here, CompanyCam has no verified reviews API, so the review ask runs on our system triggered by a job-completion signal — a completed checklist or final photo set makes a clean trigger.

What this means for your shop

If your proof of work lives in CompanyCam, you’re in strong shape: it’s the rare platform where the API covers the thing the product is actually for, with scoped keys and real event alerts. Two disciplines: be on a paid plan, and make sure anything built for you targets the new developer portal — work built against the retiring legacy API has an expiration date printed on it.