BizKitHub
DocsAPI ReferencePost/api/v1/post/view
postPostPublic API v1

/api/v1/post/view

Records one page view for a post — increments the same views_count counter that GET /post/post uses, via the shared Redis buffer flushed every 5 min.

Why a separate endpoint? When docs/ (or any consumer) serves pages via ISR or a long-lived server cache, the upstream GET /post/post is called once per cache window, not once per actual visitor. Firing this endpoint client-side after each real page load gives accurate per-visitor counts without re-fetching the full article.

GeoIP side effect: when customerRealIp is supplied (or can be inferred from Vercel edge headers), the IP is registered in brj__geo_ip. This is a best-effort operation — a lookup failure never blocks the view count. The registered record is enriched in the background by the existing geo-IP cron and will be the foundation for visitor-origin analytics in a future release.

identityId is accepted for forward-compatibility but is not yet used for unique-view deduplication. Pass the same value you use in GET /post/post.

Double-count note: if your integration calls both GET /post/post (server-side) and POST /post/view (client-side) for the same page load, the first uncached server-side fetch will count one extra view. For ISR-heavy sites this is negligible; for high-precision analytics, avoid calling GET /post/post from your renderer and rely solely on this endpoint.

postpostApiV1PostView

Parameters

1 query · JSON body

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
slugstringRequired

Canonical URL slug of the article to record a view for.

Length: 1–∞
Examplenazev-clanku
identityIdstringOptional

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

ExampleZ9CPkS2o3UV163VQn5OUv0T8BQi8Fvdg
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
state"error"Required
messagestringRequired
code"200"Required
hintstring | nullRequired
One of 2:
Variant 1
string
Variant 2
null

Response example

application/json
{
  "success": true
}

Request example

POST /api/v1/post/view

post
curl -X POST "https://api.bizkithub.com/api/v1/post/view?apiKey=PRODPGrFxpGEtrOZfuWhnoJohUYBXuOE" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
  "slug": "nazev-clanku",
  "identityId": "Z9CPkS2o3UV163VQn5OUv0T8BQi8Fvdg",
  "customerRealIp": "1.1.1.1"
}'

Need an API key?

All BizKitHub public API endpoints require authentication via API key.

Get API Key