canonical: https://jentic.com/apis/safetyculture.io/safetyculture

# SafetyCulture API

SafetyCulture (iAuditor) API for inspections, assets, groups, and safety management. The API exposes 21 endpoints secured with bearer authentication.

## For AI agents

Programmatically create group, list all groups. Covers 21 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create group
- List all groups
- Add user to group
- Remove user from group
- Bulk delete groups

## Use cases

### Developer Tools Operations

Use the SafetyCulture API to perform developer tools operations programmatically. The API provides 21 endpoints covering core functionality including create group, list all groups, add user to group.

Example prompt: Call POST /groups to create group

### Automated Assets Management

Automate assets operations by combining multiple SafetyCulture API endpoints. Agents can list all groups and then add user to group in a single workflow.

Example prompt: Call GET /groups to list all groups, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SafetyCulture API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'create group', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/groups` | Create group |
| GET | `/groups` | List all groups |
| POST | `/groups/{groupId}/users` | Add user to group |
| GET | `/groups/{groupId}/users` | List group users |
| DELETE | `/groups/{groupId}/users/{userId}` | Remove user from group |
| POST | `/groups/bulk-delete` | Bulk delete groups |
| GET | `/users/{userId}/groups` | List user groups |
| POST | `/inspections/start` | Start inspection |

## Key resources

- **Assets** — Operations related to Assets
- **Groups** — Operations related to Groups
- **Inspections** — Operations related to Inspections

## Why Jentic

- **Setup:** Wiring the SafetyCulture API by hand means handling its bearer token, attaching it to each call against api.safetyculture.io, and managing your own retries. Through Jentic you install once, import the SafetyCulture API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SafetyCulture puts the group id in the URL path (`/groups/{groupId}/users/...`), so a rule can pin your agent to one group: it can list and add users for that group and nothing else. You choose the operations it may call, so destructive ones like removing a user or bulk-deleting groups are not included unless you add them.
- **Credential handling:** Your SafetyCulture API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a group' or 'add a user to a group', and Jentic returns the matching SafetyCulture API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the SafetyCulture API use?

The SafetyCulture API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create group with the SafetyCulture API?

Yes. Use the POST /groups endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SafetyCulture API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create group through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create group'. Jentic returns the matching SafetyCulture API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SafetyCulture API have?

The SafetyCulture API exposes 21 endpoints covering assets, groups, inspections operations.

### Can I limit what my agent is allowed to do with the SafetyCulture API?

Yes. Because Jentic One is self-hosted, you decide which SafetyCulture operations and credentials your agent may use, and your own rules are enforced at execution time. SafetyCulture puts the group id in the URL path (`/groups/{groupId}/users`), so you can pin the agent to a single group and let it only list and add users there. Destructive calls like removing a user (DELETE `/groups/{groupId}/users/{userId}`) or bulk-deleting groups (POST `/groups/bulk-delete`) stay off limits unless you explicitly add them to what the agent is allowed to call.