Look up SafetyCulture users by email to route inspections and actions via the API
domain: developer.safetyculture.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with a SafetyCulture API token against https://api.safetyculture.io.
Call `POST /users/search` with a JSON body containing an `email` array, e.g. `{"email":["person@example.com"]}`.
Read the returned `users` array for each match's `id`, `email`, `firstname`, and `lastname`.
Use the returned `id` as the `id` value in an inspection-share (`POST /audits/{audit_id}/share`) or action-assignment call.
Cache resolved user IDs locally since email-to-ID lookups don't change often, to avoid repeated search calls in high-volume automations.
Known gotchas
The search is by exact email match — partial name or fuzzy search is not supported by this endpoint.
A user must already exist in your SafetyCulture organization (or be invited) before they can be found and shared with; the API does not create/invite users through this call.
Requires the token owner to have visibility into the org's user directory, which is typically an Administrator-level permission.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?