Source
Extensibility & developer surface — found from sitemap — Shopware
Checked for Shopware on 5 Oct 2026
- Page
- https://developer.shopware.com/docs/guides/plugins/plugins/framework/store-api/
- Checked
- 5 Oct 2026, 04:57 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c72846606ad3076fab2a1a8c4823de783de0fc20769e3b686e9c00c40fd7b20f
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Store API custom endpoints Report an error
“Use the Store API to add custom endpoints or extend existing ones in plugins. Store API routes are service-based and follow strict architectural conventions to ensure consistency, cacheability, and extensibility.”
-
Store API routes as services Report an error
“Define Store API controllers as services.”
-
Store API sales channel API deprecated Report an error
“Do not implement the Sales Channel API, deprecated as of 6.4.”
-
Store API route response decorator Report an error
“Response decorators must extend StoreApiResponse.”
-
Store API single object response Report an error
“A route response can only contain one object.”
-
Store API routes decoratable Report an error
“Routes may be decorated to extend behavior.”
-
Storefront controllers use store API Report an error
“Storefront controllers must not access repositories directly. Controllers must call Store API routes.”
-
Store API logic in routes Report an error
“Business logic belongs in Store API routes, not in controllers.”
-
Store API route naming Report an error
“Use named routes internally.”
Scores citing this record
- The B2B Seller Extensibility & developer surface
- The Data Protection Officer Extensibility & developer surface
- The Developer Extensibility & developer surface
- The Merchant Extensibility & developer surface
- The Operations Lead Extensibility & developer surface
- The Skeptic Extensibility & developer surface