SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations and safety platform used by frontline teams to run inspections, capture and track issues, assign corrective actions, manage assets and sites, deliver training, and provision users. Its public REST API at https://api.safetyculture.io exposes more than 380 documented operations across inspections, templates, assets, actions, issues, users, groups, schedules, training, credentials, and webhooks, secured with bearer API tokens (service-user and personal). Near real-time webhooks stream a rich catalog of inspection, action, incident, media, and training events, and SCIM 2.0 supports user provisioning via Microsoft Entra ID and Okta.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles SafetyCulture the way a machine reads it — 42 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — SafetyCulture scores 68.1/100 (exemplar), with a separate agent-readiness read of 30/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from SafetyCulture's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/safetyculture/"
title="SafetyCulture on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/safetyculture.svg"
alt="SafetyCulture Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/safetyculture/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/safetyculture/"
title="SafetyCulture on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/safetyculture/card.svg"
alt="SafetyCulture Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile SafetyCulture
Each block below is one kind of artifact we hold for SafetyCulture. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 27
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SafetyCulture Actions API
The Actions API from SafetyCulture — 30 operation(s) for actions.
SafetyCulture Apps API
The Apps API from SafetyCulture — 7 operation(s) for apps.
SafetyCulture Assets API
The Assets API from SafetyCulture — 34 operation(s) for assets.
SafetyCulture Bulk user operations API
The Bulk user operations API from SafetyCulture — 4 operation(s) for bulk user operations.
SafetyCulture Companies API
The Companies API from SafetyCulture — 9 operation(s) for companies.
SafetyCulture Credentials API
The Credentials API from SafetyCulture — 9 operation(s) for credentials.
SafetyCulture Data Feeds API
The Data Feeds API from SafetyCulture — 39 operation(s) for data feeds.
SafetyCulture Directory (Sites) API
The Directory (Sites) API from SafetyCulture — 13 operation(s) for directory (sites).
SafetyCulture Documents API
The Documents API from SafetyCulture — 10 operation(s) for documents.
SafetyCulture Groups API
The Groups API from SafetyCulture — 7 operation(s) for groups.
SafetyCulture Heads Up API
The Heads Up API from SafetyCulture — 5 operation(s) for heads up.
SafetyCulture Inspections API
The Inspections API from SafetyCulture — 26 operation(s) for inspections.
SafetyCulture Investigations API
The Investigations API from SafetyCulture — 27 operation(s) for investigations.
SafetyCulture Issues API
The Issues API from SafetyCulture — 24 operation(s) for issues.
SafetyCulture Lone Worker API
The Lone Worker API from SafetyCulture — 2 operation(s) for lone worker.
SafetyCulture Media API
The Media API from SafetyCulture — 1 operation(s) for media.
SafetyCulture OSHA API
The OSHA API from SafetyCulture — 8 operation(s) for osha.
SafetyCulture Response Sets API
The Response Sets API from SafetyCulture — 5 operation(s) for response sets.
SafetyCulture Roles API
The Roles API from SafetyCulture — 3 operation(s) for roles.
SafetyCulture Schedules API
The Schedules API from SafetyCulture — 12 operation(s) for schedules.
SafetyCulture Schedules (legacy) API
The Schedules (legacy) API from SafetyCulture — 2 operation(s) for schedules (legacy).
SafetyCulture Sensors API
The Sensors API from SafetyCulture — 7 operation(s) for sensors.
SafetyCulture Structures API
The Structures API from SafetyCulture — 11 operation(s) for structures.
SafetyCulture Templates API
The Templates API from SafetyCulture — 7 operation(s) for templates.
SafetyCulture Training API
The Training API from SafetyCulture — 24 operation(s) for training.
SafetyCulture Users API
The Users API from SafetyCulture — 14 operation(s) for users.
SafetyCulture Webhooks API
The Webhooks API from SafetyCulture — 3 operation(s) for webhooks.
Scroll within the panel for all 27 ·
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Safetyculture Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Safetyculture Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Safetyculture Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
SafetyCulture API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
s12.incidents.v1.CreateCaseRequest
JSON SCHEMAs12.incidents.v1.OSHAService.UpdateCaseBody
JSON SCHEMAUpdateScheduleItem
JSON SCHEMASecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for SafetyCulture — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/safetyculture · machine-readable index on apis.io
This is an independent, third-party profile of SafetyCulture, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.