SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform for inspections, audits, issue reporting, corrective actions, and asset management. The SafetyCulture API exposes this operational data — templates, inspections, actions, assets, schedules, and more — so it can be extracted and integrated into downstream systems.
Power end-to-end data operations for your SafetyCulture API with Nexla. Our bi-directional SafetyCulture connector is purpose-built for SafetyCulture, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to SafetyCulture or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your SafetyCulture workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a SafetyCulture credential, you need an API token from your SafetyCulture account. The SafetyCulture API authenticates each request with a bearer token sent in the Authorization header (for example, Authorization: Bearer <your-api-token>).
To generate an API token, follow these steps:
-
Sign in to the SafetyCulture web app with an account that has the permissions required to access the data you want to ingest.
-
Click your username in the lower-left corner and select My profile.
-
Click Settings in the upper-right corner, then select API tokens.
-
Click Generate API token, enter a name for the token and your account password in the pop-up window, and click Generate.
-
Click the newly created token to copy it, and store it securely. The token is shown only once, so save it before closing the window.
For long-term or shared integrations, SafetyCulture recommends generating a service user API token so that access remains stable regardless of individual user changes. Note that API tokens expire after 30 days of inactivity, after which you must generate a new one. For details on tokens and authentication, see the SafetyCulture Developer Portal and the Authentication reference.
Authenticate
Credentials required
Authenticate to SafetyCulture.
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key | Yes | Yes | API key. |
Create a credential in Nexla
-
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter your SafetyCulture API token in the API Key field. This is the token you generated in Prerequisites. It is sent as a bearer token in the
Authorizationheader for all API requests and must be kept confidential.If your API token is compromised, revoke it in your SafetyCulture account settings and generate a new one. Remember that tokens also expire after 30 days of inactivity.
For detailed information about authentication and available endpoints, see the SafetyCulture Developer Portal.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the SafetyCulture connector tile, then select the credential that will be used to connect to your SafetyCulture account, and click Next; or, create a new SafetyCulture credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common SafetyCulture endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
SafetyCulture data sources can also be manually configured to ingest data from any valid SafetyCulture API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new SafetyCulture data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.