/

Freshservice

Freshservice

Integration type

Helpdesk

What we solve

Freshservice IT teams need a fast, low-overhead way to verify a requester’s identity before performing sensitive service-desk actions (password resets, account unlocks) because tickets and email alone are easy to spoof. This integration uses Freshservice webhooks and REST APIs to trigger 1Kosmos BlockID Verify/LiveID on ticket creation, post the verification link back into the ticket, consume webhook results, and automatically update/resolve tickets (and kick off downstream automation like Entra AD password resets) once identity is verified—reducing social-engineering risk while speeding resolution.

Platform identity landscape

Freshservice (Freshworks) serves fast-scaling SMBs and mid-market companies, with a Freddy AI-powered ITSM engine. The Freshservice Marketplace lists 900+ integrations. Freshservice exposes a REST API with webhook support for ticket creation, update, and status change events.

The Freshservice integration path is the simplest in the ITSM category — a lightweight webhook-based approach requiring no low-code platform.

Freshservice ticket created: "Account locked — need password reset"
    -> Freshservice webhook: ticket.created event
    -> BlockID Freshservice Marketplace app receives webhook
    -> POST /v2/verify/sessions { requestor: email, mobile }
    <- { session_id, verification_url }
    -> Freshservice API: POST /api/v2/tickets/{ticket_id}/notes
        body: "Please verify your identity to proceed: [verification_url]"
    -> Requestor: IDV + LiveID
    <- BlockID webhook: { idv_status: "VERIFIED" }
    -> Freshservice API: PATCH /api/v2/tickets/{ticket_id}
        body: { status: 4, tags: ["IDV_VERIFIED", "AUTO_RESOLVED"]

Freshservice ticket created: "Account locked — need password reset"
    -> Freshservice webhook: ticket.created event
    -> BlockID Freshservice Marketplace app receives webhook
    -> POST /v2/verify/sessions { requestor: email, mobile }
    <- { session_id, verification_url }
    -> Freshservice API: POST /api/v2/tickets/{ticket_id}/notes
        body: "Please verify your identity to proceed: [verification_url]"
    -> Requestor: IDV + LiveID
    <- BlockID webhook: { idv_status: "VERIFIED" }
    -> Freshservice API: PATCH /api/v2/tickets/{ticket_id}
        body: { status: 4, tags: ["IDV_VERIFIED", "AUTO_RESOLVED"]

Freshservice ticket created: "Account locked — need password reset"
    -> Freshservice webhook: ticket.created event
    -> BlockID Freshservice Marketplace app receives webhook
    -> POST /v2/verify/sessions { requestor: email, mobile }
    <- { session_id, verification_url }
    -> Freshservice API: POST /api/v2/tickets/{ticket_id}/notes
        body: "Please verify your identity to proceed: [verification_url]"
    -> Requestor: IDV + LiveID
    <- BlockID webhook: { idv_status: "VERIFIED" }
    -> Freshservice API: PATCH /api/v2/tickets/{ticket_id}
        body: { status: 4, tags: ["IDV_VERIFIED", "AUTO_RESOLVED"]

Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.

Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.

Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.