/api/v1/post/create

Optional caller-supplied stable identifier for this article. When omitted (or empty), a new post is always inserted. When provided, the post is matched within the organisation by code: an existing post with the same code is updated in place, a missing one is inserted with that code attached. This makes /create idempotent for batch importers — the same call with the same code can be safely retried or used to push content updates.

Post title (single-line plain text).

Post body. HTML is preserved; whitespace is normalized.

Short summary / teaser. Stored in the locale row alongside title and content.

Post visibility. Defaults to public. Updates may change visibility; transitioning out of private triggers a publishedDate stamp if not already set.

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.

External id of the category to assign as mainCategory. On insert, when omitted the platform falls back to the first active category and attempts AI-based categorization in the background. On update, when omitted the existing category is left untouched.

Optional cuRefNo of the contact to attribute as the main author on insert. When omitted the organisation’s internal customer is used. Ignored on update.

Optional human-readable commit message recorded on the version history entry for this call. When omitted, the system fills a sensible default (e.g. Initial version via /api/v1/post/create (code=…) or Update via /api/v1/post/create (code=…)).

Optional structured key/value metadata bag merged into content__post_meta after the post upsert. Designed for external integrations (e.g. ChatSPC) that need to attach provenance — sukl_code, version_date, pdf_sha256, page_count, suspicious_pages, ingested_at, … — without operating their own database. Read it back via /api/v1/post/meta. Pass null for a key to clear it. Keys must fit 64 chars; values are strings — stringify your numbers/booleans before sending.

Optional list of blob attachments to link to the post.

On insert the supplied attachments become the post’s initial attachment set. On update they are appended to the post’s existing set — this endpoint never removes attachments. Use the admin (/bff/post/post-attachment-delete) to detach.

Duplicate tokens inside one call, and tokens that are already attached to the post, are silently collapsed — a blob is never linked twice to the same post. If any supplied token does not exist or belongs to a different organisation, the whole call is aborted before any change is written to the post.