Skip to content
Korta

FAQ

General

Section titled “General”

What is Korta?

Section titled “What is Korta?”

Korta is a full-stack URL shortener for developers and creators. It supports anonymous shortening, authenticated link management, and API-key-based integrations.

Is Korta production-ready?

Section titled “Is Korta production-ready?”

It is deployed and usable in production for portfolio-scale traffic. The project is in maintenance mode and prioritizes stability over rapid feature expansion.

Can I use it without creating an account?

Section titled “Can I use it without creating an account?”

Yes. The public endpoint allows anonymous shortening (POST /urls/public).

Why create an account then?

Section titled “Why create an account then?”

Authenticated users get private link management (create/edit/delete/list), API key generation, and dashboard-level visibility for their links.

Technical

Section titled “Technical”

What authentication methods are supported?

Section titled “What authentication methods are supported?”

Two methods:

  • Authorization: Bearer <jwt> for user sessions.
  • X-API-Key: <api_key> for integrations.

Is the API RESTful?

Section titled “Is the API RESTful?”

Yes, routes follow REST-style patterns with versioning under /api/v1.

What database and ORM are used?

Section titled “What database and ORM are used?”
  • PostgreSQL
  • Prisma ORM

How are errors returned?

Section titled “How are errors returned?”

Errors follow a consistent shape:

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Validation failed",
  "details": {}
}

Operations

Section titled “Operations”

How is rate limiting handled?

Section titled “How is rate limiting handled?”

Rate limiting is per endpoint and per IP (for example: POST /urls/public is 100/hour, POST /auth/login is 10/15 min, redirects are 300/5 min).

What is the health-check endpoint?

Section titled “What is the health-check endpoint?”

GET /api/v1/health returns:

{"status":"OK"}

Why did I see CORS errors in production?

Section titled “Why did I see CORS errors in production?”

Most CORS issues come from domain mismatch or routing configuration. Ensure:

  • Koyeb public path is /.
  • Health path is /api/v1/health.
  • FRONTEND_URL and CORS_ORIGINS match frontend domain exactly.

What are the main current limitations?

Section titled “What are the main current limitations?”
  • Free-tier infrastructure constraints.
  • Single-region dependency.
  • Basic analytics only.
  • No advanced failover/resiliency layer yet.