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

/api/v1/post/category

Returns category detail with child categories, breadcrumb, post feed, and routing info. Returns an error object if the category does not exist.

postgetApiV1PostCategory

Parameters

4 query

Query parameters

· 4
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
slugstringRequired
Examplenovinky
localestringRequired

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-oxendict → en-GB → en (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: 2–35
Examplecs
identityIdstringOptional

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

ExampleZ9CPkS2o3UV163VQn5OUv0T8BQi8Fvdg

Response schema

1 status code documented

200Success
object | object
One of 2:
Variant 1
namestringRequired
ExampleNovinky
descriptionstringRequired
ExampleNejnovější zprávy a aktuality ze světa kyberbezpečnosti.
routeobjectRequired
slugstringRequired
ExampleNovinky
localestringRequired

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-oxendict → en-GB → en (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: 2–35
Examplescsenen-GBpt-BRzh-Hans
canonicalbooleanRequired
routesobject[]Required
Each array item:
slugstringRequired
Examplenovinky
localestringRequired

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-oxendict → en-GB → en (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: 2–35
Examplescsenen-GBpt-BRzh-Hans
childrenobject[]Required
Each array item:
slugstringRequired
namestringRequired
descriptionstringRequired
postCountnumberRequired
breadcrumbobject[]Required
Each array item:
namestringOptional
ExampleNovinky
slugstringRequired
Examplenovinky
childrenany[]Required
postFeedobject[]Required
Each array item:
slugstringRequired
Examplekyber-cena-roku-2025-nejvetsi-vecer-ceske-kyberbezpecnosti-letos
titlestringRequired
ExampleKYBER CENA ROKU 2025: největší večer české kyberbezpečnosti letošního roku.
contentstringRequired
ExampleŽijeme ve světě, kde je...
perexstring | nullRequired
One of 2:
Variant 1
string
ExampleTřetí ročník vyhlášení proběhl...
Variant 2
null
publishedDateDate | string | string | number | nullRequired
One of 2:
Variant 1
Date | string | string | number
One of 4:
Variant 1
Date
Example2025-11-05T15:54:44.280Z
Variant 2
stringdate-time
Variant 3
stringdate
Variant 4
number
Variant 2
null
parentobjectOptional
namestringRequired
slugstringRequired
descriptionstring | nullRequired
One of 2:
Variant 1
string
Variant 2
null
Variant 2
state"error"Required
messagestringRequired
ExampleCategory "about" does not exist.
code"200"Required
hintstring | nullRequired
One of 2:
Variant 1
string
Variant 2
null

Response example

application/json
{
  "name": "Novinky",
  "description": "Nejnovější zprávy a aktuality ze světa kyberbezpečnosti.",
  "route": {
    "slug": "Novinky",
    "locale": "cs",
    "canonical": false
  },
  "routes": [
    {
      "slug": "novinky",
      "locale": "cs"
    }
  ],
  "children": [
    {
      "slug": "example_slug",
      "name": "example_name",
      "description": "example_description",
      "postCount": 0
    }
  ],
  "breadcrumb": [
    {
      "name": "Novinky",
      "slug": "novinky",
      "children": []
    }
  ],
  "postFeed": [
    {
      "slug": "kyber-cena-roku-2025-nejvetsi-vecer-ceske-kyberbezpecnosti-letos",
      "title": "KYBER CENA ROKU 2025: největší večer české kyberbezpečnosti letošního roku.",
      "content": "Žijeme ve světě, kde je..."
    }
  ],
  "parent": {
    "name": "example_name",
    "slug": "example_slug"
  }
}

Request example

GET /api/v1/post/category

get
curl -X GET "https://api.bizkithub.com/api/v1/post/category?apiKey=PRODPGrFxpGEtrOZfuWhnoJohUYBXuOE&slug=novinky&locale=cs&identityId=Z9CPkS2o3UV163VQn5OUv0T8BQi8Fvdg" \
  -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