Integrations & API

Your safety data, connected to the systems that run the business.

SALUS is the field-first capture layer where proof starts. Through a deep Procore integration and an official developer API, the records your crews create in the field flow automatically into the project record, your BI tools, and any enterprise workflow — with no double entry.

Complete the safety work once. Let the data appear where the business needs it.

Talk to our team Read the API docs

SField → Procore

Scheduled sync

Signed JHA — Steel ErectionProcore · DocumentsSynced

Manpower log · 8 workersProcore · Daily LogSynced

Form attachment · Grid C-12Procore · PhotosSynced

Form review · FLHA #318Procore · TasksCreated

Captured once in the field. Supported finalized records move to their configured Procore destinations on a scheduled sync.

Deep Procore sync
Official developer API
Automations & reporting
No double entry

Why integrations

Safety data should not live in a safety silo.

Mid-market contractors already run on Procore, BI tools, document systems, and enterprise reporting. The gap is rarely another dashboard — it is getting the field-verified record into the systems that already run the project and the business.

SALUS connects the safety work to that stack, so the proof your crews create shows up where decisions, audits, and billing actually happen.

Complete the safety work once, then let the data appear where the business needs it.

The dashboard claims compliance

Office-first tools show green dashboards — but the field record they depend on is often incomplete, late, or stuck in a separate app.

The field re-enters the same data

Crews fill out the safety form, then someone retypes it into the project system. Double entry is slow, lossy, and the first thing to get skipped.

The proof never reaches the business

Signed forms, photos, sign-ins, and corrective actions sit in a safety silo instead of the project record, the data warehouse, and the owner report.

How SALUS connects

Two ways to connect SALUS to your stack.

A purpose-built deep integration for the system most contractors run on, and an open API for everything else.

→

Deep integration

Procore

A scoped, two-way connection: selected Procore projects become SALUS sites, while supported SALUS forms, review requests, attachments, and manpower fields move to their configured destinations in the Procore project record.

See the Procore integration

→

Developer platform

The SALUS API

The official developer API to read your safety data out of SALUS and write into the areas SALUS supports — forms, projects, workers, certificates, assets, incidents, documents, and more — for BI, data warehouses, and custom workflows.

Explore the API

Automations

Trigger certificate alerts, overdue corrective-action escalations, digests, and stakeholder updates automatically.

Scheduled reporting

Deliver weekly, monthly, owner, insurer, and executive reports without manual assembly.

Procore integration

The best field engine for your Procore brain.

SALUS does not replace Procore — it completes it. Procore dashboards can claim compliance, but field teams hit friction with safety modules and the data ends up incomplete. SALUS is the mobile field engine crews actually use.

Selected project information flows from Procore into linked SALUS sites. Supported, finalized field records then move from SALUS into agreed Procore tools — without claiming that every object synchronizes in both directions.

Accurate field intelligence, flowing into your system of record.

Procore → SALUS

Selected projects

Projects enabled for SALUS sync can become linked SALUS sites.

Project identity

The Procore project ID maintains the connection between the two records.

SALUS field engine

Capture in the field · move supported records

SALUS → Procore

Submitted formsFiled in configured Procore Documents folders.

Forms requiring reviewCreated as Procore Tasks for the review workflow.

Form attachmentsCopied to the Procore Photos tool.

Manpower fieldsMapped into pending Procore Daily Log manpower entries.

The Procore integration created more tangible value in the form of time back to the field. We eliminated double-entries.

Justin ItulleField Integration Manager, Willmeng Construction

400K

users

150K

sites

field data points

14K

companies

See SALUS + Procore live Read the technical integration guideTrusted by Procore teams like Turner Construction, McFarland, and Willmeng.

Developer API

An official API for your safety data.

The SALUS Developer API is the official way to read your safety data out of SALUS and write into the areas SALUS supports. It is built for system-to-system integration where access control and authentication are handled upstream.

SALUS API · v0.11-beta

# Authenticate with client credentials, then call the API
GET /v1/form_instance?status=signed
Authorization: Bearer <access_token>

{
  "data": [
    {
      "id": "fi_8f2c…",
      "title": "JHA — Steel Erection",
      "status": "signed",
      "site_id": "site_4471",
      "signed_at": "2026-06-17T09:14:00Z",
      "pdf": "/v1/form_instance/fi_8f2c…/download"
    }
  ]
}

Pick a languageShellNodePythonRubyPHPJavaC#

Authentication

Built for company-owner access

The API requires a company-owner account and uses standard authorization grants — Classic or Client Credentials — so your integration authenticates once and runs system-to-system.

Built for BI

Aggregate endpoints for analytics

Group-by aggregation endpoints across forms, incidents, projects, assets, and certificates feed dashboards and data warehouses without exporting raw rows by hand.

Machine-readable

OpenAPI & llms.txt

Full OpenAPI specs and an llms.txt index make the reference easy to consume — for your tools and for AI agents.

What you can access

Forms & submissions

Pull JHAs, PTPs, inspections, and signed PDFs — with images, signatures, and bulk export.

GET /v1/form_instance

Projects & workers

Create projects, sync rosters, and add or remove the workers on each site.

POST /v1/project

Users & roles

Provision workers, sync company profiles, and manage roles and permissions.

POST /v1/user

Certificates

Track, create, upload, and download credentials, providers, and certificate types.

GET /v1/certificate

Assets & equipment

Search the fleet by name, VIN, or model and group by status, model, or color.

GET /v1/asset

Incidents

Surface incidents, injuries, and near misses by site, severity, status, or user.

GET /v1/incident

Corrective actions

Read open actions, named owners, assigned companies, and closure status.

GET /v1/corrective_action

Documents

Search and download any document in the account by name, path, or user.

GET /v1/document

Public access URLs

Generate shareable links for forms, certs, assets, and a site check-in bundle.

POST /v1/public_access/bundle

Read the docs Get started

Automations & reporting

Set it once. Let the data move on its own.

The connected record is only useful if it reaches people on time. SALUS turns field activity into alerts, escalations, and reports that fire automatically.

Certificate alerts

Notify workers and supervisors before a credential expires — and block the high-risk work until it is renewed.

Corrective-action escalations

Escalate overdue actions to the right owner automatically so nothing closes without proof.

Scheduled digests

Send weekly, monthly, owner, insurer, and executive reports on a schedule, with no manual assembly.

Stakeholder updates

Push the right safety summary to GCs, owners, and auditors the moment the data changes.

Use cases

What teams build when safety data stops being stuck.

Eliminate double entry

Field safety records sync into Procore automatically, so crews and admins stop retyping the same data into two systems.

Feed your BI & data warehouse

Pull connected safety data through the API and aggregation endpoints into Looker, Power BI, Tableau, or your warehouse.

Prequal & audit-ready exports

Generate the document, certificate, and training packages owners and auditors ask for — without rebuilding the record.

Owner & insurer reporting

Schedule the leading-indicator reports that strengthen prequal standing and insurance conversations.

Keep the project record current

Move supported safety records into the agreed Procore tools without retyping them.

Build custom internal tools

Use the API to power dashboards, mobile views, and workflows specific to how your business runs.

FAQ

Common questions.

Does SALUS integrate with Procore?

Yes. Selected Procore projects can become linked SALUS sites. Supported SALUS workflows then move submitted forms to configured Documents folders, forms requiring review to Tasks, form attachments to Photos, and mapped manpower fields to pending Daily Log entries. The connection is scoped; it does not synchronize every Procore and SALUS object.

Does SALUS replace Procore?

No. Procore remains the project system of record. SALUS gives crews a field-first way to complete safety work, then returns supported finalized records to agreed locations in Procore.

Do SALUS Inspections, Observations, or Incidents sync to Procore?

No. Those integrations are not currently confirmed. The maintained technical integration guide distinguishes the supported workflows from possible future integration points.

Is there a developer API?

Yes. The SALUS Developer API is the official way for other systems to read data from SALUS or write into the areas SALUS supports. It is designed for system-to-system integration rather than direct end-user access.

How is the API authenticated?

The API requires a company-owner-level account and uses standard authorization grants — typically the Classic or Client Credentials flows — so access control and authentication are handled upstream of the integration.

What data can I access through the API?

Forms and submissions (including signed PDFs and signatures), projects and workers, users and roles, certificates, assets and equipment, incidents, corrective actions, documents, industry classifications, public access URLs, and group-by aggregation endpoints for analytics.

Is the API documented for tools and AI agents?

Yes. SALUS publishes full OpenAPI specifications plus an llms.txt index of every page and endpoint in Markdown, so both your tooling and AI agents can consume the reference directly.

Can I automate alerts and reports?

Yes. SALUS can trigger certificate alerts, overdue corrective-action escalations, scheduled digests, and stakeholder updates, and deliver weekly, monthly, owner, insurer, and executive reports automatically.

Integrations & API

Connect SALUS to the systems you already run.

Capture the record once in the field. Sync it into Procore, query it through the API, and let automations move it where the business needs it.

Request a demo

Deep Procore sync · Official developer API · Automations & reporting