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 (e.g. 1.1.1.1), IPv6 (e.g. 2001:4860:4860::8888)
Normalization:
::1,0.0.0.0,localhost(or empty value) is normalized to127.0.0.1- Invalid values are rejected (the API expects a valid IP string).
If provided, the system can resolve additional context (reverse DNS, geolocation, ASN, proxy/hosting flags) via our internal VikiTron GEO/IP resolver. Learn more
1.1.1.1Request body
application/jsonmessagestringRequiredMessage body from the customer. Must be at least 10 characters (rejects one-word noise) and at most 5000 characters (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.
jan@barasek.comcategorySlugstringOptionalCategory slug for routing the ticket.
offercustomerEmailstringOptionalContact 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.
jan@barasek.comcustomerPhonestringOptionalContact 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ášek