/api/v1/post/rss

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

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.

Optional main category route slug to filter posts. Only posts whose mainCategory matches this slug will be included in the feed. Same semantics as /post/feed.

Optional tag code to filter posts. Only posts that have this tag assigned will be included. The tag must be active and belong to the same organisation. Same semantics as /post/feed.

Optional author profile slug (the contact's profileSlug — i.e. shop__contact.external_id as exposed by /post/post). Filters posts by main_author_id matching this contact.

When true, each <item> includes the full HTML body of the post as <content:encoded><![CDATA[…]]></content:encoded> (the standard RSS content-module extension). When false or omitted, the current teaser-only behavior is preserved.