Source

Extensibility & developer surface — found from sitemap — Vendure

Checked for Vendure on 3 Nov 2026

Page: https://docs.vendure.io/current/framework/developer-guide/extend-graphql-api
Checked: 3 Nov 2026, 15:43 UTC
How we may use it: Public page, crawling permitted

Technical details

type: page
http status: 200
content hash: sha256:667326f2f6f895c2e16d27a42f89cdc2797df92b4aae434ee32efa0564ec66f7
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Graphql schema extensions Report an error

“Extension to the GraphQL API consists of two parts: Schema extensions. These define new types, fields, queries and mutations. Resolvers. These provide the logic that backs up the schema extensions.”
Graphql independent API extension Report an error

“The Shop API and Admin APIs can be extended independently:”
Plugin shop API extensions Report an error

“shopApiExtensions: { schema: schemaExtension, resolvers: [TopProductsResolver], },”
Graphql override builtin resolvers Report an error

“It is also possible to override an existing built-in resolver function with one of your own.”
Graphql union error results Report an error

“Union types are commonly returned from mutations in the Vendure APIs.”
Graphql custom scalars builtin Report an error

“By default, Vendure bundles DateTime and a JSON custom scalars (from the graphql-scalars library).”
Graphql custom scalars from version Report an error

“From v1.7.0, you can also define your own custom scalars for use in your schema extensions:”
Permission decorator on mutations Report an error

“we have used the @Allow() decorator to ensure that only users with the UpdateSettings permission can call this mutation.”
Transaction decorator Report an error

“We have also wrapped the resolver in a transaction using @Transaction(), which is a good idea for any mutation which modifies the database.”

2 facts read from this page are not shown because they could not be confirmed on the page as captured.