Skip to content
AnyBiz AnyBiz Documentation

API Reference

This section contains the API documentation for integrating with AnyBiz.

Overview

Section titled “Overview”

AnyBiz provides a RESTful API built with oRPC (OpenAPI-compatible RPC). The API supports:

  • Authentication - Session-based authentication via Better Auth
  • Organization Context - All API calls operate within an organization context
  • Type-Safe Contracts - Full TypeScript support with Valibot validation

API Categories

Section titled “API Categories”

Authentication

Section titled “Authentication”
  • Login/Logout
  • Registration
  • Session management

Organization

Section titled “Organization”
  • Organization management
  • Member management
  • Subscription management

Features

Section titled “Features”
  • Point of Sale (POS)
  • Invoices (list, get, create, finalize, send to eFaktura)
  • Business Partners
  • Settings (organization, eFaktura, fiscalization)
  • Events SDK (/api/events/sdk/*) for external map embedding and checkout flow — see the TicketMap SDK integration guide
  • Internal: POST /api/internal/sef-subscribe (cron; requires X-Cron-Secret or Authorization: Bearer with SEF_CRON_SECRET)

Getting Started

Section titled “Getting Started”

To use the AnyBiz API:

  1. Authenticate - Obtain a session by logging in
  2. Select Organization - Set the active organization context
  3. Make API Calls - Use the documented endpoints

OpenAPI Specification

Section titled “OpenAPI Specification”

The full OpenAPI specification can be generated from the oRPC contracts. Run pnpm docs:generate-api from the repository to regenerate it.

Base URL

Section titled “Base URL”
https://api.anybiz.com/api

For local development:

http://localhost:3000/api

Authentication

Section titled “Authentication”

All API requests require authentication. Include the session cookie in your requests:

Terminal window
curl -X GET "https://api.anybiz.com/api/organization/current" \
  -H "Cookie: session=your-session-token"

Rate Limiting

Section titled “Rate Limiting”

API calls are subject to rate limiting. Please ensure your integration handles rate limit responses appropriately.

Error Handling

Section titled “Error Handling”

All API errors follow a consistent format:

{
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable error message"
  }
}

Common error codes:

  • UNAUTHORIZED - Authentication required
  • FORBIDDEN - Insufficient permissions
  • NOT_FOUND - Resource not found
  • VALIDATION_ERROR - Invalid request data