canonical: https://jentic.com/apis/arventa.com.au/arventa # Arventa WHS Monitor API Jentic publishes the only available OpenAPI specification for Arventa WHS Monitor API, keeping it validated and agent-ready. Arventa WHS Monitor is a cloud-based Work Health and Safety compliance platform used by Australian businesses to manage workers, sites, chemicals, incident reports, and risk assessments. The API exposes 58 endpoints across 15 resource areas including checklists, audit logs, departments, locations, and chemical storage tracking. Bearer token authentication protects all calls and the API supports paginated retrieval for high-volume operational data. ## For AI agents Manage WHS compliance records - workers, incident reports, risk assessments, chemical storage, and audit logs - for Australian Work Health and Safety obligations. ## Scope Does not handle payroll, accounting, or HR onboarding - use for Work Health and Safety compliance, incident reporting, and chemical tracking only. ## Capabilities - Create and update incident reports tied to specific sites and locations - Retrieve risk assessments and link them to remediation actions - Track chemical storage and SDS links by site and storage location - Manage worker records, departments, and role assignments across multiple sites - Pull audit logs filtered by date range for compliance reporting - Create checklist instances from templates and submit completed inspections - List subscriptions and roles to drive access control decisions ## Use cases ### Incident Reporting Workflow Capture workplace incidents directly from a mobile or chat interface and file them against the correct site, location, and department in WHS Monitor. The API accepts incident reports through the IncidentReport endpoints and links them to corrective actions, removing the lag between an event happening on the floor and being logged in the compliance system. Suitable for organisations managing dozens to hundreds of sites where central HSE teams need real-time visibility. Example prompt: Create an incident report for site ID 42 describing a slip-and-fall at location 'Warehouse B' on 2026-06-08 and confirm the report ID returned ### Chemical Inventory and SDS Tracking Maintain an accurate register of chemicals stored across multiple sites, with each entry tied to its Safety Data Sheet link. The Chemical/SDSLinkByStorageAsync and Chemical/StorageBySiteAsync endpoints let agents pull current storage records on demand, supporting audits, regulator submissions, and emergency response queries. Useful where chemicals move between storages frequently and SDS links need to stay current. Example prompt: Fetch all chemicals stored at site ID 7 with their SDS links and return a summary by storage area ### Risk Assessment Lifecycle Manage risk assessments from creation through review, with associated controls and corrective actions tracked via the Actions endpoints. Agents can list outstanding assessments, push updates after a review meeting, and surface overdue items to safety managers. Reduces the manual reconciliation between spreadsheets and the WHS Monitor record of truth. Example prompt: List all RiskAssessments for department 12 and identify any without an associated open Action ### Agent-Driven Compliance Monitoring An AI agent integrated through Jentic can poll Arventa WHS Monitor for new incidents, overdue checklists, and audit log changes, then summarise the state of compliance for a safety manager every morning. The agent uses Jentic's intent search to locate the right Arventa endpoint without browsing API docs, and Jentic's credential vault keeps the bearer token isolated from the agent's context. Example prompt: Through Jentic, retrieve audit logs for the last 7 days and incidents from the last 24 hours, then produce a morning compliance briefing ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /v1/IncidentReport | Retrieve incident reports | | GET | /v1/AuditLogs | Retrieve audit logs with optional date filtering | | GET | /v1/Chemical/StorageBySiteAsync | Retrieve chemical storage by site | | GET | /v1/Chemical/SDSLinkByStorageAsync | Fetch SDS links by storage | | POST | /v1/Checklist | Create a new checklist | | GET | /v1/Locations | Query locations | | POST | /v1/Locations | Create a new location | | GET | /v1/Actions | Retrieve actions with pagination | ## Key resources - **IncidentReports** — Create and retrieve workplace incident records - **RiskAssessments** — Manage risk assessments and associated controls - **Chemicals** — Track chemical storage by site and link to SDS documents - **Checklists** — Manage checklist templates and submitted inspection records - **Workers** — Manage worker records and assignments - **Locations** — Create, update, and query physical locations under sites - **AuditLogs** — Read audit log entries with date filtering - **Actions** — Track corrective and preventive actions ## Why Jentic - **Setup:** Wiring Arventa WHS Monitor by hand means handling its bearer auth against its Australian host for incident, chemical, and checklist calls. Through Jentic you install once, import the Arventa WHS Monitor API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Arventa's operations target incidents, chemicals, and locations through query and body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as listing incident reports or reading chemical storage. You choose the operations it may call, so posting a checklist is not included unless you add it. - **Credential handling:** Your Arventa bearer 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 'log a workplace incident' or 'list chemicals by site', and Jentic returns the matching Arventa operation with its input schema so the agent calls the right endpoint without reading the docs. ## Related APIs - **SafetyCulture** — SafetyCulture (iAuditor) is a global WHS inspection and audit platform with broader template and checklist coverage than Arventa. - **Drata** — Drata handles SOC 2, ISO 27001, and HIPAA compliance automation alongside Arventa's WHS focus. - **PagerDuty** — PagerDuty escalates urgent incidents to on-call responders once Arventa logs them. ## FAQ ### Why is there no official OpenAPI spec for Arventa WHS Monitor API? Arventa does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Arventa WHS Monitor API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Arventa WHS Monitor API use? The API uses HTTP bearer token authentication. Tokens are passed in the Authorization header. When called through Jentic, the bearer token is stored in the Jentic credential vault and never enters the agent's context - Jentic injects it at execution time. ### Can I log workplace incidents through the Arventa WHS Monitor API? Yes. The /v1/IncidentReport endpoints support retrieving and managing incident reports tied to sites, locations, and workers. Incidents can be linked to corrective actions tracked under /v1/Actions for full lifecycle visibility. ### What are the rate limits for the Arventa WHS Monitor API? The OpenAPI specification does not document explicit rate limits. Treat the API as standard tier - implement exponential backoff on HTTP 429 responses and cache GET results where compliance data changes infrequently, such as department lists and checklist templates. ### How do I retrieve chemical SDS information through Jentic? Search Jentic for 'list chemical SDS links by storage' - the /v1/Chemical/SDSLinkByStorageAsync operation will be returned. Load the operation schema, supply the storage identifier, and execute. Jentic handles authentication and returns the structured response to the agent. ### Does the Arventa API support pagination for large result sets? Yes. Endpoints like /v1/Actions and /v1/Assets/{type} accept pagination parameters in the query string. Agents should iterate through pages when pulling audit logs or organisation-wide datasets to avoid timeouts on large estates. ### Can I limit what my agent is allowed to do with the Arventa WHS Monitor API? Yes. Because Jentic One is self-hosted, you decide which Arventa operations your agent may call and which credentials it may use, and you can restrict it to only what it needs, such as listing incident reports or reading chemical storage by site. Arventa's operations act on incidents, chemicals, and locations through query and body parameters rather than a resource id in the URL path, so scoping is defined by the specific operations you grant. If you do not add write operations like posting a checklist or creating a location, the agent cannot perform them.