Parameters
9 query
Query parameters
· 9apiKeystringRequiredYour 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
PRODPGrFxpGEtrOZfuWhnoJohUYBXuOEquerystringRequiredFull-text search query entered by the client. Can contain words, phrases or year numbers, e.g. "2025".
2025countrystringOptionalOptional ISO 3166-1 alpha-2 country code of the visitor (e.g. "CZ"). When set, the response is filtered to posts whose per-country / per-continent allowlist matches the visitor — a post targeted at continent "EU" matches every EU country, and a post with no rules stays globally available. When omitted, the filter is disabled and every post is returned regardless of geo settings. The API does NOT infer the country from the caller's IP; it is up to the caller to resolve and supply it. Case-insensitive. Unknown codes are rejected with HTTP 400 (PUBLIC_COUNTRY_CODE_UNKNOWN). The pseudo code INT selects the international (region-less) edition of a multi-region publication: only posts WITHOUT any country / continent rule.
CZlocalestringRequiredCommunication 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-GBvs.en-US(British vs. American spelling)pt-PTvs.pt-BR(European vs. Brazilian Portuguese)zh-Hansvs.zh-Hant(Simplified vs. Traditional Chinese)sr-Latnvs.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.
csidentityIdstringOptionalLogged user identity (from your frontend cookies). Learn more
Z9CPkS2o3UV163VQn5OUv0T8BQi8Fvdglimitstring | integerOptionalMaximum number of items to return in items, ordered by relevance descending. When omitted, the server default of 100 is applied. Hard-capped at 200 regardless of a larger value being requested.
100offsetstring | integerOptionalNumber of ranked results to skip, for pagination ("load more"). Default 0. Honoured by the in-memory search used for organisations with a small post corpus; the large-corpus SQL search always starts at 0 (check offset in the response).
0mainCategorystringOptionalOptional main category route slug to restrict the search to posts assigned to that category. The slug is resolved in the requested locale against the organisation category routes; when it resolves to no category, the search returns zero results.
novinkyorderBy"relevance" | "date"OptionalOrdering of the returned items. Defaults to relevance (score descending, current behavior). date returns the most-recently-published matches first (published_date DESC NULLS LAST, then inserted_date DESC). The score field is still populated in both modes.
relevance