Authenticate and create/retrieve Activity records (incidents, near misses, audits) via the Cority Enviance EMS REST API
domain: api.enviance.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Note that use of the API requires an express Cority Enviance Connectors license from Enviance/Cority; the Swagger spec at `https://api.enviance.com/Swagger.svc/swagger.json` is publicly viewable, but calls will fail authentication without a contracted license.
Obtain a session with `POST /ver2/AuthenticationService.svc/sessions`, sending a JSON body `{"userName": "...", "password": "..."}`; the response returns a SessionId.
Send that SessionId on every subsequent call as `Authorization: Enviance <SessionId>` (an OAuth-token flow is also available via `POST /ver2/AuthenticationService.svc/oauthtoken` using a refresh token).
Create an Activity (e.g., a near-miss or incident record) with `POST /ver2/ActivityService.svc/activities`, supplying `name`, `templateIdOrName`, and a `fields` array of `{name, values}` pairs matching the target template's configured fields.
Retrieve, update, or delete a specific activity with `GET`/`PUT`/`DELETE /ver2/ActivityService.svc/activities/{activityIdOrName}`, addressing it by its ID or unique name.
Call `DELETE /ver2/AuthenticationService.svc/currentsession` to explicitly end the session when finished.
Known gotchas
The optional `EnvApi-Systemid` header lets a login target a specific sub-system instead of the account's default ("Home") system — confirm which system should receive the call before omitting it.
Field values in `fields[].values` must match the names/options actually configured in the target template in your Enviance instance — this is a template-driven platform, not a fixed global schema.
This is the legacy "Enviance" product's REST API (api.enviance.com), now marketed under Cority Enviance/CorityOne; it is a distinct host/product from Cority's other EHSQ platform APIs.
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?