Kora

Developers

Know the moment a ticket changes

Kora sends a signed webhook to your endpoint for ticket and help center events, with delivery logs and retries so nothing is silently lost.

Webhook deliveriesExample workspace
  • ticket.created200
  • ticket.assigned200
  • ticket.sla_breachRetry scheduled
  • ticket.resolved200

Signed with HMAC-SHA256Logs kept 30 days

Quick answer
Kora sends webhooks for 10 events: eight ticket events and two help center events. Add a secret token and each request is signed with HMAC-SHA256 so you can verify it came from Kora, and failed deliveries are logged and retried. You can create up to 10 webhooks per workspace, and webhooks are free.

Ten events across tickets and articles

Get an event when a ticket is created, updated, assigned, claimed, resolved, closed, reopened or breaches its SLA target, and when a help center article is published or updated.

  • 8 ticket events
  • 2 help center events
  • Up to 10 webhooks per workspace
Webhook deliveriesExample workspace
  • ticket.created200
  • ticket.assigned200
  • ticket.sla_breachRetry scheduled
  • ticket.resolved200

Signed with HMAC-SHA256Logs kept 30 days

Signed, so you can trust them

Add a secret token to a webhook and every request is signed with HMAC-SHA256 in the X-Kora-Signature header. Webhook secrets are encrypted with AES-256-GCM, so a stored secret is not readable in plain text.

  • HMAC-SHA256 signatures
  • Secrets encrypted with AES-256-GCM
  • Verify before you act
Public APIExample workspace
curl https://api.usekora.app/public/v1/tickets \
-H "X-Workspace-ID: <your workspace ID>" \
-H "X-Secret-Key: <your secret key>"
{ "success": true,
"tickets": [ { "id": 14, "title": "…", "status": "Open" } ] }

Logs and retries, so nothing vanishes

Delivery logs show what was sent and how your endpoint responded, and are kept for 30 days. Failed deliveries go to a retry queue.

  • Delivery logs kept 30 days
  • Automatic retries
  • Free to use
Webhook deliveriesExample workspace
  • ticket.created200
  • ticket.assigned200
  • ticket.sla_breachRetry scheduled
  • ticket.resolved200

Signed with HMAC-SHA256Logs kept 30 days

How it works

  1. 1Add an endpoint

    Register a URL and choose the events you want.

  2. 2Verify the signature

    If you set a secret token, check the HMAC-SHA256 signature in X-Kora-Signature.

  3. 3Respond quickly

    Return a success response. Failures are retried.

  4. 4Check the logs

    Use delivery logs to debug anything that did not arrive.

$0.10
per ticket created
Unlimited
members, free
6
roles
1,100
free credits to start

For developers

The ten events

Eight ticket events and two help center events.

Ticket events

  • ticket.created
  • ticket.updated
  • ticket.resolved
  • ticket.closed
  • ticket.reopened
  • ticket.assigned
  • ticket.claimed
  • ticket.sla_breach

Help center events

  • article.published
  • article.updated

Delivery

  • Signed with HMAC-SHA256 when a secret token is set
  • Delivery logs kept for 30 days
  • Failed deliveries are retried

What it costs

$0

Webhooks do not use credits.

Calculation, not a customer

CostCalculation, not a customer
Webhooks
Free
Delivery logs and retries
Free
Up to 10 webhooks per workspace
Included
Total
$0

Suggested starting setup

A suggestion, adjust to your work

Categories

One webhook per system you notify

Roles

  • Owner and Admin: manage webhooks

SLA targets

PriorityFirst responseResolution
Critical1 hour1 day
High4 hours2 days
Medium1 day5 days
Low2 days10 days

The sla_breach event fires after a target is breached, not before.

What Kora does not do yet

  • Email-to-ticket: planned
  • Native Slack integration: planned
  • MCP server for AI assistants: planned

Common questions

Which events can I subscribe to?

Ten: ticket.created, ticket.updated, ticket.resolved, ticket.closed, ticket.reopened, ticket.assigned, ticket.claimed, ticket.sla_breach, article.published and article.updated.

How are webhooks signed?

If you add a secret token to a webhook, every request is signed with HMAC-SHA256 (X-Kora-Signature: t=timestamp,v1=signature).

What happens if my endpoint is down?

Failed deliveries are logged and go to a retry queue.

How long are delivery logs kept?

30 days.

How many webhooks can I have?

Up to 10 per workspace.

Do webhooks cost credits?

No, webhooks are free.

Are webhook secrets stored safely?

Yes, they are encrypted with AES-256-GCM.

Connect Kora to your systems

1,100 free credits. No card.

  • No credit card
  • Unlimited members
  • No contract
New ticketExample workspace
Describe the issue in your own words…
MediumOtherCreate ticket

$0.10 per ticket created. 1,100 free credits to start.