Parameters
2 query · JSON body
Query parameters
· 2apiKeystringRequiredYour BizKitHub API key (passed as GET parameter).
Key format: A 32-character string matching: ^(PROD|DEV_|ROOT)[A-Za-z0-9]{28}$
Prefixes: PROD (production key), DEV_ (individual developer), ROOT (system key with no limits). Learn more
PRODPGrFxpGEtrOZfuWhnoJohUYBXuOEcustomerRealIpstringOptionalUser IP address used for GEO/IP intelligence.
Accepted formats:
- IPv4 dot-decimal, e.g.
1.1.1.1(4 octets, 0–255, no leading zeros). - IPv6 as defined by RFC 4291 — full
2001:0db8:0000:0000:0000:0000:0000:0001, zero-compressed2001:db8::1, IPv4-mapped::ffff:1.2.3.4, or scoped literals. Both upper- and lower-case hex are accepted.
Server-side canonicalization (ipNormalize in core/src/lib/network/ipNormalize.ts):
- Valid IPv4 is passed through verbatim.
- Valid IPv6 is lowercased (RFC 5952 §4.3).
- IPv4-mapped IPv6
::ffff:X.X.X.Xis unwrapped to plain IPv4 (RFC 4291 §2.5.5.2) so1.2.3.4and::ffff:1.2.3.4share onebrj__geo_iprow. - Loopback aliases (
::1,0.0.0.0,localhost, empty string) collapse to127.0.0.1. - Junk values that fail both IPv4 and IPv6 validation are silently rejected and replaced with
127.0.0.1(loopback).
On the wire: every response returns the canonicalized form — clients can safely rely on lowercase IPv6 and the plain-IPv4 unwrap when de-duping or joining. Server-originated writers (activity log, session log, ban list) resolve the visitor IP via resolveClientIp / resolveClientIpOrNull — always native IPv6 on Vercel Edge (there is no auto-mapping to ::ffff:X.X.X.X).
Enrichment: the system resolves reverse DNS, geolocation, ASN, mobile/proxy/hosting/Tor flags via our VikiTron GEO/IP resolver for both address families. Learn more
1.1.1.1Request body
application/jsonmessagestringRequiredMessage body from the customer. At least 10 characters (rejects one-word noise). At most 5000 characters for messageFormat: text and 15000 for markdown (formatting syntax and links take room); a full report fits, spam floods do not.
Hello, how are you?subjectstringOptionalSubject line for the support ticket.
Request from JannoticestringOptionalInternal note (not visible to customer).
Internal noticesendToEmailstringOptionalContact email address.
The system validates the input as a standard email address and automatically applies normalization and canonicalization.
All API responses return the normalized form, and each email address is unique per organisation within the system.
Phone-only contacts: Since 2026-06-10 a contact may exist without an e-mail when it was registered only by phone (e.g. imports of phone-only records). Responses that expose such contacts use API_EMAIL_NULLABLE instead, where this field can be null. Endpoints that accept e-mail as input still require a valid value here — phone-only creation goes through admin-only import / BFF flows.
[email protected]categorySlugstringOptionalCategory slug for routing the ticket. By default the same slug is also assigned to the submitting contact as a contact group (new and existing contacts alike; a missing group is auto-created). If your website grants rights based on contact groups, pass assignCategoryGroup: false or use a category slug that is not used as a permission group.
offerassignCategoryGroupbooleanOptionalWhether categorySlug is also assigned to the contact as a contact group. Default true (historic behaviour). Pass false to only route the ticket and leave the contact groups untouched.
truecustomerEmailstringOptionalContact email address.
The system validates the input as a standard email address and automatically applies normalization and canonicalization.
All API responses return the normalized form, and each email address is unique per organisation within the system.
Phone-only contacts: Since 2026-06-10 a contact may exist without an e-mail when it was registered only by phone (e.g. imports of phone-only records). Responses that expose such contacts use API_EMAIL_NULLABLE instead, where this field can be null. Endpoints that accept e-mail as input still require a valid value here — phone-only creation goes through admin-only import / BFF flows.
[email protected]customerPhonestringOptionalContact phone number in international (national) format.
Preferred format: +<country_code> <local_number>
- Leading plus sign (
+) is required - Followed by the country calling code (e.g.
420) - One space after the country code
- Full local number without spaces
Example: +420 777123456
This format ensures unambiguous storage, validation, and compatibility with SMS, calling, and third-party integrations (e.g. Twilio, WhatsApp, CRM systems).
+420 777123456customerFirstNamestringOptionalJancustomerLastNamestringOptionalBarášekurgentbooleanOptionalReporter's felt-urgency flag. Pass true when the contact form exposes an 'urgent for me' checkbox and the visitor ticked it. Persisted to pm__issue.user_urgency_hint and forwarded to the AI triage classifier as a soft input (never authoritative — content still decides the final priority). Keep unset / false for automated submissions.
falseattachmentsstring[]OptionalOptional file attachments uploaded alongside the ticket. Send as multipart/form-data with repeated attachments parts. Policy: up to 5 files, max 10 MB each, max 25 MB combined. Only images, PDFs, plain text/CSV, Office and OpenDocument files are accepted — archives and executables are rejected via magic-byte detection even when the extension is renamed. Each accepted file is stored privately in core__blob and linked to the created issue via pm__issue_attachment.
FilesOptional file attachments uploaded alongside the ticket. Send as multipart/form-data with repeated attachments parts. Policy: up to 5 files, max 10 MB each, max 25 MB combined. Only images, PDFs, plain text/CSV, Office and OpenDocument files are accepted — archives and executables are rejected via magic-byte detection even when the extension is renamed. Each accepted file is stored privately in core__blob and linked to the created issue via pm__issue_attachment.
inlineImagesstring[]OptionalImages embedded in a markdown message (messageFormat: markdown). The N-th part replaces the image source token bkh-inline-image:N in the message, e.g. . PNG, JPEG, WebP or GIF, max 5 MB each, max 10 images. Stored publicly (unguessable URL) so they render in the description everywhere, and also listed as ticket attachments. Unreferenced or failed images are dropped from the body.
FilesImages embedded in a markdown message (messageFormat: markdown). The N-th part replaces the image source token bkh-inline-image:N in the message, e.g. . PNG, JPEG, WebP or GIF, max 5 MB each, max 10 images. Stored publicly (unguessable URL) so they render in the description everywhere, and also listed as ticket attachments. Unreferenced or failed images are dropped from the body.
branchSlugstringOptionalBranch the request is about (slug from /branch/list), when the visitor picked one. The ticket then appears in /support/my-issue-list of the branch technicians (unless it is confidential). An unknown or inactive slug is silently ignored and the ticket is created without a branch.
plzen-skvrnanymessageFormat"text" | "markdown"Optionaltext (default): plain text, line breaks preserved. markdown: GitHub-flavoured markdown from a rich editor (headings, lists, code, tables, links, images); rendered through the same sanitizer as every ticket body.
text