Automation platforms
Any automation platform or script that can send an HTTP request can drive SafeHanded through the public API or the generic webhook. That’s enough to create requests, react to events and trigger close-to-purge from whatever holds your work: a helpdesk without an adapter, a shared mailbox, a form or a project board.
What the API gives a flow
Section titled “What the API gives a flow”| Step | Endpoint | Scope |
|---|---|---|
| Connection test | GET /ping | any |
| Create a request | POST /requests | requests:write |
| Mark ticket status | POST /tickets/{ref}/status | tickets:write |
| Look up a request | GET /requests/{id} | requests:read |
| React to events | webhook subscription per request.* event | webhooks:write |
Close-to-purge from anything
Section titled “Close-to-purge from anything”Mark ticket status is the universal close-to-purge path: let your platform watch whatever holds your work, and mark the ticket closed when it’s done. As with the generic webhook, these statuses are unverified — they purge only if you’ve enabled Trust unverified webhooks in Policy, unless the ticket is linked through an adapter that can read it back (e.g. Halo, ConnectWise), in which case SafeHanded verifies before acting.
Setting it up
Section titled “Setting it up”- Create a SafeHanded API key (Settings → API) with the scopes above, scoped to a client if appropriate.
- In your platform, add an HTTP step that sends the key as described in API authentication.
- Build your flow — e.g. “when a ticket is tagged done, mark the SafeHanded ticket closed”, or “when a form is submitted, create a request”.