Skip to content
Q

Guides

Guides

Walkthroughs for common integration tasks.

These guides walk you through common tasks with the QUiCK API. The patterns below use real endpoints; the complete, runnable list lives in the API Reference.

Bulk-uploading expense documents

POST /2/expenses/create/ accepts up to 5 documents per call, Base64-encoded:

bash
curl -X POST https://api.quick.riport.co.hu/2/expenses/create/ \
  -H "Authorization: Token $QUICK_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "expenses": [
      { "filename": "invoice1.pdf", "content": "<base64>" },
      { "filename": "invoice2.pdf", "content": "<base64>" }
    ],
    "source": "public_api"
  }'

The response returns the identifiers of the processed expenses: { "processed": [90231, 90232] }.

Walking a paginated list

List endpoints respond with a count / next / previous / results envelope. To read everything, follow the next URL until it becomes null:

bash
curl "https://api.quick.riport.co.hu/1/expenses/?page=1&page_size=100" \
  -H "Authorization: Token $QUICK_API_TOKEN"

Choosing a page size

A larger page_size means fewer requests, but a slower response per page. Values between 50 and 200 are usually a good compromise.

Selecting the company context

If your token can serve more than one company, the Quick-Company-Id header selects the target. Omit it and the company is inferred from the token. See the Authentication page for details.

Next steps

The conceptual background is on the Core concepts page, and the full endpoint list can be browsed and tried in the API Reference.