BizKitHub
DocsAPI ReferenceSupport/api/v1/support/issue/{externalId}/comment
postSupportPublic API v1

/api/v1/support/issue/{externalId}/comment

Appends a new comment to the ticket, attributed to the ticket reporter. Used by the reply form on the customer-facing ticket page on bizkithub.com. Applies min/max length, per-issue 24h rate limit, and an LLM spam check; spam replies are stored with a badge (or silently dropped once per-issue / per-IP thresholds are exceeded) and do not reopen closed tickets.

supportpostApiV1SupportIssueByExternalIdComment

Parameters

1 path · 1 query · JSON body

Path parameters

· 1
externalIdstringRequired

The 16-char alphanumeric external identifier of the issue.

Length: 16–16
Examplea1B2c3D4e5F6g7H8

Query parameters

· 1
apiKeystringRequired

Your 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

ExamplePRODPGrFxpGEtrOZfuWhnoJohUYBXuOE

Request body

application/json
messagestringRequired

Customer reply text. Server-side rules: leading/trailing whitespace is trimmed, then the payload is truncated at 5000 chars (silent), then rejected with MESSAGE_TOO_SHORT if fewer than 3 non-whitespace chars remain. A per-issue 24h volume ceiling and an LLM spam classifier are applied before insert.

Length: 1–10000
ExampleThanks for the update — issue confirmed on my side too.
customerRealIpstringOptional

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-compressed 2001: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.X is unwrapped to plain IPv4 (RFC 4291 §2.5.5.2) so 1.2.3.4 and ::ffff:1.2.3.4 share one brj__geo_ip row.
  • Loopback aliases (::1, 0.0.0.0, localhost, empty string) collapse to 127.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

Examples1.1.1.12001:4860:4860::8888

Response schema

1 status code documented

200Success
object | object
One of 2:
Variant 1
success"true"Required
Variant 2
success"false"Required
error"NOT_FOUND" | "INVALID_EXTERNAL_ID" | "NO_REPORTER" | "MESSAGE_TOO_SHORT" | "RATE_LIMITED" | "UPSTREAM_ERROR"Required
messagestringOptional

Human-readable explanation for the failure. Present on RATE_LIMITED and UPSTREAM_ERROR — the customer-facing UI should prefer this over its own generic fallback so the reason is visible.

Response example

application/json
{
  "success": true
}

Request example

POST /api/v1/support/issue/{externalId}/comment

post
curl -X POST "https://api.bizkithub.com/api/v1/support/issue/a1B2c3D4e5F6g7H8/comment?apiKey=PRODPGrFxpGEtrOZfuWhnoJohUYBXuOE" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
  "message": "Thanks for the update — issue confirmed on my side too.",
  "customerRealIp": "1.1.1.1"
}'

Need an API key?

All BizKitHub public API endpoints require authentication via API key.

Get API Key