Which data you can bind to your component, where that data may be requested, and which fields arrive in the body. The list is the central catalogue itself — this page is not written by hand.
How the boundary works
1
Data
The contract lives in the central CONTENT_SOURCES row: allowed_page_types, allowed_component_types and depends_on_customer. No special case is hard-coded per source name.
2
Panel
The merchant is offered only the sources that fit the page and component type the component sits in; an out-of-boundary source is never listed.
3
Runtime
An out-of-boundary call does not quietly return empty — it fails closed with 400. The real message is printed on each source card below.
• If a boundary field is empty there is NO restriction: the source may be used on every page and in every component type. This is not a default, it is the data contract itself.
• If a translation is missing the text comes back empty and a "translation missing" marker appears on screen; there is no silent fallback to Turkish.