Skip to content

Getting started

Overview

Get to know the QUiCK accounting API, how it is structured, and how this developer hub is organised.

QUiCK is a modern accounting and finance platform whose public REST API automates the whole bookkeeping workflow: partner records, incoming and outgoing invoices (expenses and incomes), documents, payments, taxes, salaries and the accounting master data. This hub gives you the conceptual guides, the interactive endpoint reference and a recipe collection for everyday integration tasks.

What the QUiCK API does

The API covers accounting administration end to end — the focus is not on issuing invoices, but on synchronising accounting data two ways with an external ERP, webshop or your own system.

  • Expenses (expenses) and incomes (incomes) — list, create and update incoming and outgoing documents
  • Partners (partners) — manage customer and vendor records, matched by tax number
  • Documents (documents) — upload files (PDF, image) and attach them to an expense or income
  • Payments (payments) and cash accounts / bank accounts (accounts)
  • Taxes (taxes, tax-codes) and salaries (salaries, monthly-salaries, monthly-taxes)
  • Accounting master data (v2): ledger numbers (ledger-numbers), VAT categories (vat-categories), expense and revenue types, tags, audit-xml export

Core principles

  • REST + JSON, predictable HTTP status codes, paginated lists (page / page_size)
  • Token-based authentication — every call carries the Authorization: Token <token> header
  • Two API versions run side by side: /1/ for the stable core operations, /2/ for the extended, often bulk accounting operations
  • Machine-readable OpenAPI 3.0 specification — see the API Reference, where every call can be tried straight from the browser
  • Content negotiation: most endpoints answer both as ?format=json (default) and ?format=html

Environment and access

The public API is served on the api. subdomain: https://api.quick.riport.co.hu. Authentication uses a company-scoped API token — the Authentication page walks you through creating one.

What you will find in this hub

Three separate surfaces, all built from the same content model.

Documentation

Conceptual guides, recipes, troubleshooting and terminology. Start here if QUiCK is new to you.

API Reference

The interactive endpoint reference generated from the OpenAPI specification. Calls can be tried directly in the browser with your own API token.

Admin

The internal backoffice for editing and publishing documentation and for the hub settings.

Your first integration, step by step

A typical integration takes four steps:

  1. Create an API token in the QUiCK app (Company settings → API Tokens)
  2. Identify the company — call GET /2/company-info/ to read your company details, including its id
  3. Read data — list partners (GET /1/partners/) or expenses (GET /1/expenses/)
  4. Write data — record a new expense or income, attach a document

Start by checking the connection

Before writing anything, run a GET /1/pulse/ call — it verifies that your token is valid and returns the aggregated balance of the company's cash and bank accounts. Details on the Getting started page.