CompanyCam API

Name: CompanyCam API API
Brand: CompanyCam API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationbearer41 EndpointsREST

For Agents

Manage CompanyCam projects, photos, tags, comments, checklists, and webhooks for field-service and construction crews from a single API.

Quickstart

Get started with CompanyCam API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"upload a photo to a CompanyCam project"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CompanyCam API API.

Create projects and attach photos with location and tag metadata

Upload field photos and assign them to a project, user, and tag set

Run a checklist against a project from a saved template

Group users into crews and manage their project access

Comment on photos to coordinate punch lists between field and office

GET STARTED

Start building with CompanyCam API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for CompanyCam API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for CompanyCam API, keeping it validated and agent-ready. The CompanyCam API lets contractors and field-service teams attach geo-tagged, time-stamped photos to projects and share them with crews, clients, and back-office systems. Through the API agents can manage projects, upload and tag photos, run checklists from templates, group team members, and subscribe to webhooks for project and photo events. It is built around the workflow of construction, roofing, restoration, and trades businesses where photo evidence drives invoicing, insurance, and quality control.

Use Cases

Patterns agents use CompanyCam API API for, with concrete tasks.

★ Field Photo Capture and Project Documentation

Capture geo-tagged photos at a job site and attach them to the right CompanyCam project so the office team has a real-time visual record. The API exposes /projects and /projects/{project_id}/photos for creation, plus tag and comment endpoints for context. Restoration and roofing companies use this to build insurance evidence packages without manual photo organization.

Create a new project named '123 Main St Roof Replacement', then upload three photos tagged 'before' to that project

Quality Control Checklists

Run a standardized checklist against every completed job to enforce quality and compliance. The API offers /checklists and /templates so agents can spawn a checklist instance from a template and report progress. Service contractors use this to prove that every install step was photographed and signed off before the customer is invoiced.

Find the 'Final Walkthrough' template, create a checklist on project 88421, and list its required photo items

CRM and Accounting Webhook Integration

Push CompanyCam events into a CRM, accounting, or job-management system the moment they happen in the field. The /webhooks endpoints let agents subscribe to project, photo, comment, and tag events and receive structured payloads. This avoids polling and keeps the office system synchronized with the crew's actual progress.

Register a webhook subscription for project.photo.created events to forward each new photo URL to the company's billing system

Agent-Driven Field Operations via Jentic

Let an AI assistant handle photo and project bookkeeping by voice or chat for crews on site. Through Jentic an agent searches for the right CompanyCam operation, loads its schema, and executes the upload or status update without the developer wiring auth or pagination. This is well suited to mobile or in-vehicle assistants where the crew prefers spoken commands.

On voice command 'log this as the finished gutter on the Henderson job', find project 'Henderson', upload the active photo, and tag it 'after'

Key Endpoints

41 endpoints — jentic publishes the only available openapi specification for companycam api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/projects

Create a project

GET

/projects/{id}

Retrieve a project

POST

/projects/{project_id}/photos

Upload a photo to a project

GET

/photos/{id}

Retrieve a photo with tags and metadata

POST

/photos/{photo_id}/tags

Tag a photo

POST

/photos/{photo_id}/comments

Comment on a photo

POST

/webhooks

POST

/checklists

Create a checklist from a template

POST

/projects

Create a project

GET

/projects/{id}

Retrieve a project

POST

/projects/{project_id}/photos

Upload a photo to a project

GET

/photos/{id}

Retrieve a photo with tags and metadata

POST

/photos/{photo_id}/tags

Tag a photo

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

CompanyCam bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped execution token and Jentic injects the bearer at call time, so the raw token never enters the model context.

Intent-based discovery

Agents search Jentic with intents like 'upload a photo to a project' and Jentic returns the matching CompanyCam operation with its parameter schema, so the agent can call POST /projects/{project_id}/photos without browsing docs.

Time to first call

Direct integration: 1-2 days for auth, multipart photo uploads, webhook signing, and pagination. Through Jentic: under 1 hour via search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Procore

Construction project management platform that consumes field data for budgeting, RFIs, and submittals

Use Procore alongside CompanyCam when the project office runs Procore as the system of record and you need photos to flow into Procore documents.

Complementary

Smartsheet

Spreadsheet-driven work management for project schedules and trackers

Use Smartsheet to track schedule and budget while CompanyCam captures the visual record on the job site.

Alternative

Cloudinary Upload API

General-purpose image upload, transformation, and CDN delivery

Choose Cloudinary when you need a generic photo pipeline with transformations rather than a construction-specific project model.

FAQs

Specific to using CompanyCam API API through Jentic.

Why is there no official OpenAPI spec for CompanyCam API?

CompanyCam does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CompanyCam API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the CompanyCam API use?

The API uses HTTP bearer authentication. Pass your CompanyCam personal access token or OAuth access token in the Authorization header as 'Bearer {token}'. Through Jentic the token is stored encrypted in the vault and injected at execution time.

Can I upload photos with the CompanyCam API?

Yes. Use POST /projects/{project_id}/photos to attach a photo to a specific project, or POST /photos for top-level photo creation. Photos can carry tags via POST /photos/{photo_id}/tags and comments via POST /photos/{photo_id}/comments.

What are the rate limits for the CompanyCam API?

CompanyCam enforces a default rate limit of 300 requests per minute per token. Sustained bulk operations should add backoff on HTTP 429 responses; Jentic surfaces these as structured errors rather than silently retrying.

How do I create a project with the CompanyCam API through Jentic?

Run the Jentic search query 'create a CompanyCam project', load the returned operation (POST /projects), and execute it with name, address, and assigned users in the request body. The created project id is returned for use in photo uploads.

Can I subscribe to project events via webhooks?

Yes. POST /webhooks registers a subscription for events such as project.created, project.photo.created, and comment.created. CompanyCam will POST signed payloads to the URL you provide; verify the signature header before trusting the payload.