BizKitHub
DocsAPI ReferencePost/api/v1/post/history
getPostPublic API v1

/api/v1/post/history

Returns the commit log for a post: every revision recorded in content__post_history, newest first.

A post with multi-locale content (e.g. cs + en + de) has independent revision streams per language. Pass locale=cs to scope to one language, omit to get all languages mixed; either way each item exposes its own locale field.

Designed so external consumers (e.g. ChatSPC) can present a version timeline without operating their own database. Each entry carries the version handle, timestamp, locale, snapshot title, optional commit message and the byte size of the stored content blob. The HTML body itself is fetched on demand via /api/v1/post/history/version.

postgetApiV1PostHistory

Parameters

3 query

Query parameters

· 3
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
idstringRequired

Post public id (content__post.external_id).

Example6IU2SWgP76FO2UXw
localestringOptional

Communication locale code — controls the language of textual data (product names, descriptions, articles, storefront UI, transactional e-mails).

Preferred format: BCP 47 language tag — language[-Script][-REGION]. Use the full tag whenever the script or region matters:

  • en-GB vs. en-US (British vs. American spelling)
  • pt-PT vs. pt-BR (European vs. Brazilian Portuguese)
  • zh-Hans vs. zh-Hant (Simplified vs. Traditional Chinese)
  • sr-Latn vs. sr-Cyrl (Latin vs. Cyrillic Serbian)

Backwards-compatible fallback: the bare two-letter ISO 639-1 code (cs, en, pl, …) is accepted indefinitely — legacy clients that only send the language subtag continue to work unchanged.

Resolution algorithm (server-side): the input is resolved against the supported locale list via the [RFC 4647 Lookup] progressive-fallback strategy — trailing subtags are stripped one by one until a supported locale is found. Example: en-GB-oxendicten-GBen (matched). If no subtag combination is supported, the request is rejected.

Currently supported locales: cs, en, fr, it, pl, de, sk, sv, es, zh, ja, uk, da, hu, ro, nl, pt, fi, nb, hr. Region-specific variants (e.g. en-GB, pt-BR) are accepted and resolved to their base language when the exact variant is not registered separately.

Length: 235
Examplecs

Response schema

1 status code documented

200Success
object | object
One of 2:
Variant 1
postIdstringRequired

Echo of the post external id.

localestring | nullRequired
One of 2:
Variant 1
string

Echo of the locale filter, or null when none was applied.

Variant 2
null
itemsobject[]Required
Each array item:
idstringRequired

Version handle (16 chars). Pass to /history/version to read the body.

ExamplevErSiOnHaNdLe123
insertedDateDate | string | string | numberRequired
One of 4:
Variant 1
Date
Variant 2
stringdate-time
Variant 3
stringdate
Variant 4
number
localestringRequired

Locale code of this revision (e.g. "cs", "en").

titlestringRequired

Snapshot of the post title at this revision.

commitMessagestring | nullRequired
One of 2:
Variant 1
string

Optional human commit message; null for auto-versions.

Variant 2
null
contentSizenumberRequired

Byte size of the content blob.

authorobjectRequired
idstring | nullRequired
One of 2:
Variant 1
string

cuRefNo of the author contact.

Variant 2
null
namestringRequired

Display name of the author.

Variant 2
state"error"Required
messagestringRequired
code"200"Required
hintstring | nullRequired
One of 2:
Variant 1
string
Variant 2
null

Response example

application/json
{
  "postId": "example_postId",
  "items": [
    {
      "id": "vErSiOnHaNdLe123",
      "locale": "example_locale",
      "title": "example_title",
      "contentSize": 0,
      "author": {
        "name": "example_name"
      }
    }
  ]
}

Request example

GET /api/v1/post/history

get
curl -X GET "https://api.bizkithub.com/api/v1/post/history?apiKey=PRODPGrFxpGEtrOZfuWhnoJohUYBXuOE&id=6IU2SWgP76FO2UXw&locale=cs" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY"

Need an API key?

All BizKitHub public API endpoints require authentication via API key.

Get API Key