SafetyCulture API Documentation

This is the complete API documentation for connecting to the SafetyCulture API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet SafetyCulture: Run inspections, manage actions, and resolve issues in SafetyCulture. Keep reading to get started.

Quickstart

Before you run your first SafetyCulture request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one SafetyCulture connection — create or choose one in Connections. Note its connectionId.

Every SafetyCulture action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/safetyCulture/latest/actions/{actionSlug}

You need a MindCloud API Key and a SafetyCulture connection. Then call an action such as Generate Inspection Deep Link:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/safetyCulture/latest/actions/generate-inspection-deep-link" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected SafetyCulture account that should run the action. MindCloud stores and refreshes the SafetyCulture credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

SafetyCulture actions

All 30 published actions for this SafetyCulture version. Each page documents the endpoint, arguments, and response controls.

• POSTAdd Comment to Issue Timeline
• PUTComplete Inspection
• POSTCreate Action
• POSTCreate Issue
• POSTCreate Webhook
• GETGenerate Inspection Deep Link
• GETGet Action
• GETGet Inspection
• GETGet Inspection Answers
• GETGet Inspection Details
• GETGet Inspection Web Report Link
• GETGet Issue
• GETGet Template
• GETGet Template by Inspection
• GETList Actions
• GETList Groups and Organizations
• GETList Issues
• GETList Webhooks
• GETRetrieve Selected Media
• GETSearch Modified Inspections
• GETSearch Modified Templates
• PUTSet Inspection Owner
• PUTSet Inspection Site
• POSTStart Inspection
• PUTUpdate Action Assignees
• PUTUpdate Action Due Date
• PUTUpdate Action Priority
• PUTUpdate Action Status
• PUTUpdate Inspection
• PUTUpdate Issue Status

Related apps

More Support apps on the Universal API, behind the same REST shape. Or browse all apps.

TrelloClickUpZendeskQuoIntercomEventbriteTickTickLinear