Queek docs
App capabilities

App capabilities

What a Queek app can do today, by area: the capabilities you can build with, how to reach each one, what is missing and the workarounds, plus example apps.

Your app is built from capabilities: the things the platform lets an app read, write, extend or listen to. Find what you need below. Each capability shows how you reach it (routes, scopes, webhooks and manifest entries), what is missing where it is only partly available and, where there is a gap, a workaround. New to apps? Start with Build an app.

76 capabilities: 61 available, 2 partly available, 13 not yet available. 7 more are not offered by design.

How to read this catalogue

  • Available: works as described. Anything worth knowing is listed under Good to know.
  • Partly available: some of it works. The entry says what works and lists what is missing, with a workaround where there is one. Read it before you design around it.
  • Not yet available: the platform does not offer it to apps today. Not yet available and workarounds lists each one with its workaround.
  • Not offered by design: Queek does not offer it on purpose. The entry says why and what to use instead. It is not on the roadmap. See Not offered by design.

Capabilities at a glance

Every capability, by area and status. Each name links to its entry, with the routes, scopes and limits. Capabilities Queek deliberately does not offer are listed under the table.

AreaAvailablePartly availableNot yet available
OrdersOrders read, create, import and status—Returns and exchanges
InventoryInventory, purchase orders and stock alerts——
CustomersCustomers and followers
Segments, tags and consent
Customer wishlists
——
Discounts and couponsDiscounts and coupons create/publish
Shopper coupon redemption on the storefront
Transform cart lines and bundlesApp checkout validation rules
Loyalty and gift cards—Gift cards and store credit—
PaymentsRefund an order
Payout and settlement reads
Register an app payment provider
Refund and payment events
—Create and resolve payment sessions
Shipping and fulfilmentFulfil shipped orders
Shipment tracking writes
Static shipping zones and rates
—Live carrier rates at checkout
TaxTax rows through the app API—App-calculated tax at checkout
Subscriptions——Recurring purchases
B2B——Company catalogs and price lists
Markets and translationsTranslated commerce content—Regional catalogs and display currency
Data syncBulk export and change feed
Idempotency, cursors and rate policy
——
Sales channelsProduct feed and external order import——
StorefrontProduct-page app blocks
Site-wide storefront embeds
Shopper identity to apps
Compose storefront pages
Storefront app proxy (read)
Storefront proxy writes
App-scoped product search
—Shopper account extensions
Run consent-aware tracking pixels
ContentBlog-post reads and markdown writes——
ReviewsProduct reviews: import, read, reply and moderate——
ConversationsConversation and message API for apps——
DashboardMerchant alerts (in-app bell)
App details page data
Embedded app page with session token
Declared app nav and pins
Dashboard sheet blocks, actions and print
——
Merchant APIForms and collected records
Shopper text declarations
Metafields, metaobjects and app data
Order status, payment approval and riders
Priced add-on groups on products
Products, variants and images
Apps read and update their own collected records
Booking requirements sheet
Staff directory read
——
Developer toolsCommand-line app flow
Dev stores and test data
App SDK (install, session, scopes)
AI builder toolkit and live capacity doc
——
AuthenticationApp-credential API
Install lifecycle handoffs
Optional scopes (request at runtime)
Embedded session tokens
——
WebhooksAbandoned-cart topics
Orders, products, customers, inventory, locales webhooks
Delivery retries, replay and ordering
Lifecycle as subscribable topics
Erasure and redaction topics
——
PlatformAnalytics query and app events
App-owned files and uploads
Realtime channel for apps
Registerable sales channels
App versions, review and release
—Workflow automation
App billing and usage metering
POS extensions

Not offered by design

These are deliberately not offered. Each says why and what to use instead.

CapabilityWhy and what to use instead
Loyalty points ledgerApps keep their own points ledger and reward customers with discount codes created through the Merchant API.
Tailor checkout delivery optionsQueek presents one resolved Delivery option per order; shape the offer with shipping zones and the store’s own delivery settings.
Manage storefront theme assetsQueek does not let apps inject scripts into storefronts or edit theme files. Use storefront embeds and product-page app blocks instead.
Send shopper messagesApps send through their own email or SMS provider. Queek provides consent state and events, not a send API.
Active cartsCarts belong to the shopper session. Apps do not read live carts; they see the order once it is placed.
Call an AI runtime from an appApps bring their own model. Queek does not host a model for apps to call.
Checkout UI extensionsCheckout stays one platform path so the price and the payment are exactly what the shopper saw; collect extra input on product blocks, through order attributes, or on an app page before checkout.

Browse by area

Example apps and the capabilities they use

These are examples, not a list of allowed apps. Combine capabilities for your own idea.

Platform guarantees

What stays true while you build. Each row links to the page that states it in full.

AreaWhat you can rely onRead more
VersioningOne major version, v1, that only grows: endpoints and fields may be added, and nothing is removed, renamed or retyped.Versioning and errors
DeprecationsA retirement is announced on the responses themselves, with Deprecation, Sunset and Link headers, before it stops working.Versioning and errors
ChangesEvery change to the Storefront API and the Merchant API is recorded, newest first.Changelog
WebhooksDeliveries are signed with Standard Webhooks and retried up to 8 attempts in total; delivery is at-least-once, so dedupe on webhook-id.Webhooks
Idempotency and limitsSend an Idempotency-Key on writes: the same key and body replay the stored response for 24 hours. Rate limits answer 429 with Retry-After.Idempotency and rate limits
ScopesA key holds scopes and scopes are its whole permission: an operation outside them is a 403 insufficient_scope.Merchant API scopes
SandboxDev stores have their own _test_ keys; their orders never touch real money, real customers or real deliveries.Dev stores
Review and listingEvery app is reviewed before it is listed publicly; updates are reviewed again when they add a sensitive capability, and a screencast of the app is part of every submission.App review and distribution
SupportAsk in GitHub Discussions, email the developer team, or check the status page.Support

Status labels and how this catalogue is kept accurate are explained in Stability and status.

For tools and AI agents

The same data is published in machine-readable form: capabilities.json and llms.txt.

On this page