Calendar QR code

Scan it and the event lands in the calendar, with the time zone handled properly.

curl -X POST "$DOATHING_API/v1/codes/qr-event" \
  -H "x-api-key: $DOATHING_KEY" \
  -H "content-type: application/json" \
  -d '{"title": "Product launch", "start": "2026-10-01T09:00:00", "end": "2026-10-01T10:30:00", "timezone": "Europe/London", "location": "Studio 4"}'

Scan it and the event lands in the calendar, with the time zone handled properly.

Generate a QR code carrying an iCalendar VEVENT with timezone-correct start and end times.

Response

The result carries your remaining balance alongside it, so you can track spend without a second call.

{
  "title": "Product launch",
  "start_utc": "20261001T080000Z",
  "end_utc": "20261001T093000Z",
  "duration_minutes": 90,
  "request_id": "37f01edb-0163-42a1-ac51-0acaef979800",
  "credits_remaining": 96
}

Cost

2 credits per call, whether it is run from the site or from the API — the credential differs, the price does not. A new account starts with 20 credits.

A rejected request still costs a credit: the authorizer decrements before the tool validates. A call rejected for a missing or invalid key is free.

Parameters

Generated from the endpoint’s own validation, so this is exactly what it accepts. A body field goes at the top level; an option goes inside options.

Name	In	Type	Default	Notes
title *	body	string	—
start *	body	string (ISO 8601)	—	ISO 8601, for example 2026-10-01T09:00:00.
end *	body	string (ISO 8601)	—	ISO 8601. Must be after the start.
timezone	body	string	"UTC"	e.g. UTC, Europe/London, Europe/Dublin, Europe/Paris
location	body	string	—
description	body	string	—
error_correction	options	string	"M"	one of L, M, Q, H
scale	options	integer	8	Pixels per module. 1 to 40
border	options	integer	4	0 to 20
dark	options	string	"#000000"
light	options	string	"#FFFFFF"