BizKitHub
DocsAPI ReferenceSupport/api/v1/support/my-issue-status
postSupportPublic API v1

/api/v1/support/my-issue-status

E.g. close a ticket solved by phone. Nothing is sent to the customer.

Access rule ISSUE_ACCESS (evaluated on every call): the caller is the contact behind identityId in the organisation of apiKey. A ticket is accessible when it belongs to that organisation, is classified as not spam, and

  • A (assignment): it is assigned to the caller's contact (also confidential tickets), or
  • B (branch): its branch is an active branch the caller operates (shop__branch_person role technician, manager or owner), the ticket is not confidential (securedTicket / hidden from the branch) and it was not handed back to the head office.

There is no owner (root) shortcut and contact groups (fransiza, trainer, …) never grant access. An inaccessible and a non-existent externalId answer the same 403 ISSUE_FORBIDDEN. A missing or invalid identityId answers 401.

supportpostApiV1SupportMy-issue-status

Parameters

2 query · JSON body

Query parameters

· 2
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
identityIdstringOptional

Logged user identity (from your frontend cookies). Learn more

ExampleZ9CPkS2o3UV163VQn5OUv0T8BQi8Fvdg

Request body

application/json
externalIdstringRequired

Opaque 16-char ticket id (externalId from /support/my-issue-list).

Length: 1–32
ExampleQr0MZ0vYnp8xMYgs
status"done" | "progress"Required
notestringOptional

Required for done, 3 to 2000 characters. Stored as an internal note authored by the caller.

Length: 0–5000
ExampleVyřešeno telefonicky, zámek resetován.
customerRealIpstringOptional

User 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-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

5 status codes documented

200Success
success"true"Required
statusCategoryCode"done" | "progress"Required

Response example

application/json
{
  "success": true
}

All documented status codes

· 5

Request example

POST /api/v1/support/my-issue-status

post
curl -X POST "https://api.bizkithub.com/api/v1/support/my-issue-status?apiKey=PRODPGrFxpGEtrOZfuWhnoJohUYBXuOE&identityId=Z9CPkS2o3UV163VQn5OUv0T8BQi8Fvdg" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
  "externalId": "Qr0MZ0vYnp8xMYgs",
  "note": "Vyřešeno telefonicky, zámek resetován.",
  "customerRealIp": "1.1.1.1"
}'

Need an API key?

All BizKitHub public API endpoints require authentication via API key.

Get API Key