Kora

Developers

Build on Kora, not around it

Create tickets, read data and connect your own systems through a public REST API with key authentication and generous daily limits.

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" } ] }
Quick answer
Kora has a public REST API with more than 20 endpoints. You authenticate with a workspace ID and a secret key sent as headers. API usage costs 1 credit per 400 responses. A funded wallet allows 50,000 requests a day and an empty wallet allows 5,000, and reads are not blocked for credits.

Two headers, no OAuth dance

Send your workspace ID and secret key with each request. Secrets are stored hashed, so Kora cannot show a lost secret again, only replace it.

  • X-Workspace-ID and X-Secret-Key
  • Secrets stored hashed
  • More than 20 endpoints
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" } ] }

Usage you can predict

API usage is 1 credit ($0.10) per 400 responses. A funded wallet allows 50,000 requests a day, an empty wallet 5,000, and reads are not blocked for credits, though the daily cap still applies.

  • 1 credit per 400 responses
  • 50,000 requests a day funded
  • Reads are not blocked for credits; the daily cap applies
Cost at $0.10 per ticketCalculation, not a customer
  • 100 tickets$10
  • 500 tickets$50
  • 1,000 tickets$100

Members are unlimited and free, so the bill follows tickets only.

Pairs with webhooks and the forms widget

Pull data in with the API and push events out with signed webhooks. Collect customer requests with the forms widget and handle them in Kora.

  • 10 webhook events
  • 2 KB forms widget
  • Embedded sessions for your own team
Webhook deliveriesExample workspace
  • ticket.created200
  • ticket.assigned200
  • ticket.sla_breachRetry scheduled
  • ticket.resolved200

Signed with HMAC-SHA256Logs kept 30 days

How it works

  1. 1Copy your workspace key

    Find it in settings. Owners and admins can regenerate it; the new value is shown once.

  2. 2Call the API

    Send the workspace ID and secret key as headers.

  3. 3Create and read tickets

    Connect forms, scripts or internal tools to Kora.

  4. 4Add webhooks

    Receive an event whenever a ticket changes.

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

For developers

The essentials

Full endpoint reference is in the docs.

Authentication

  • X-Workspace-ID: your workspace ID
  • X-Secret-Key: your secret key

Limits

  • Funded wallet: 50,000 requests a day
  • Empty wallet: 5,000 requests a day
  • Reads are not blocked for credits; the daily cap applies
  • Ticket creation stops when the wallet is below -10 credits

Pricing

  • 1 credit ($0.10) per 400 API responses
  • Ticket created through the API: 1 credit
  • Webhooks, forms widget: no fee of their own

What it costs

$30 a month

Plus 1 credit for each ticket you create.

Calculation, not a customer

CostCalculation, not a customer
120,000 API responses in a month
300 credits = $30
Daily request allowance
50,000 with a funded wallet
Total
$30 a month

Suggested starting setup

A suggestion, adjust to your work

Categories

Your workspace has one secret key: regenerate it if it leaks and store it in a secrets manager

Roles

  • Owner and Admin: manage API keys
  • Agent: work the tickets your code creates

SLA targets

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

Keep API keys out of public code and shared documents.

What Kora does not do yet

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

Common questions

How do I authenticate?

Send your workspace ID in X-Workspace-ID and your secret key in X-Secret-Key.

How much does the API cost?

1 credit ($0.10) per 400 responses.

What are the rate limits?

50,000 requests a day with a funded wallet and 5,000 with an empty wallet.

How many endpoints are there?

More than 20.

Are my keys stored safely?

API secrets are stored hashed.

Can I create tickets through the API?

Yes. A ticket created through the API costs 1 credit like any other.

Is there an email-to-ticket endpoint?

No. Email-to-ticket is planned and not available yet.

Get your API key

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.