Skip to main content
The manifest is the single document Weelkit reads to learn what your destination supports. It is fetched over HTTPS, validated against the protocol allowlist and limits, and summarized into a schema fingerprint.

Location

Weelkit fetches the manifest from your connection’s HTTPS base URL joined with a manifest path:
  • The default manifest path is /.well-known/weelkit-publishing.json.
  • A custom path must be same-origin and start with /. Absolute URLs pointing elsewhere are rejected.

Example

Schema reference

string
required
Must be weelkit-custom-publishing.v2.
object
required
Identity of your destination.
object
required
What your destination supports. Weelkit only performs operations you declare.
array
required
The content types Weelkit can publish into. An administrator selects one during setup.
object
required
Same-origin paths, each starting with /.
object
Maps Weelkit’s status vocabulary onto yours. Weelkit sends your value in the publish request’s status field, and recognizes it when it reads an item back, without regard to case. When omitted, the values are draft and published. Values are 1 to 32 letters, digits, -, _ or ., and the two must differ. A value outside that alphabet rejects the manifest; it is never replaced by a default.
object

Images, limits and nested fields

Images travel as URLs, so a cover image is a url field and its alt text is a string field beside it. See Publishing.

Strict reading

Weelkit reads the manifest exactly or not at all. Text beyond its bound, an option without a value, a repeated option value, a status word outside the allowed alphabet, a limit that is not a number, or a flag that is not true or false rejects the manifest with a message naming the field. Nothing is shortened, skipped or replaced by a default.

After discovery

An administrator selects one publishable content type as the primary destination. Weelkit does not treat every other content type as a reference. It fetches records only for types targeted by a reference declaration on a field in the selected primary type. The target type must declare read: true. Weelkit computes a schema fingerprint over the manifest’s normalized structure and pins the saved mapping to it. If you change the manifest later, the fingerprint changes and publishing pauses for a mapping review — see Schema and limits.