Skip to content
littleworksdocs

Explore the documentation

Meet LittleworksA small backend for the Shopify task you and your agent are already working on.Connect your agentApprove access once, then return to the conversation where your task started.Build with an agentThe operating guide for an agent using Littleworks as part of an existing Shopify task.Write a workA JavaScript handler, a small manifest, and an immutable version each time you deploy.Store dataDocument collections with a small API, scoped automatically to the work that uses them.Call ShopifyUse Shopify’s GraphQL API directly, with credentials held by Littleworks.Expose an endpointConnect an existing frontend to a work through a small JSON API.MCP tool referenceTen tools to inspect, deploy, run, and manage the backend for a connected store.Inspect and troubleshootFind the relevant run, understand the failure, and make the next change deliberately.Limits and securityThe current runtime boundaries, data isolation model, and execution allowances.
Shopify admin
Browse documentation
Build
Markdown

Expose an endpoint

Connect an existing frontend to a work through a small JSON API.

Choose the entry point

TriggerWho can invoke it
callableAn authenticated merchant or store-scoped agent through Littleworks. No public HTTP function route.
HTTP, auth: "public"Anyone who can reach the endpoint, subject to input validation, origin policy, and traffic limits.
HTTP, auth: "merchant"An authenticated merchant or store-scoped agent. This is not customer-account authentication.

Declare an HTTP trigger

Manifest trigger
{
  "trigger": {
    "type": "http",
    "method": "POST",
    "auth": "public",
    "origins": [
      "https://your-store.example"
    ]
  }
}

Replace the example origin with the exact origin of the frontend, including its scheme. Declare GET or POST. POST accepts a JSON object; GET supplies query parameters as strings. Set an appropriate inputSchema for those values.

deploy_function returns the endpoint URL for an HTTP work. Use that URL instead of constructing a path from a shop domain. Preview and Live have different URLs and data.

Call from your frontend
const response = await fetch(workUrl, {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ message: "Hello" }),
});

if (!response.ok) throw new Error("The request could not be completed");
const result = await response.json();

Here, workUrl is the URL returned by deployment. The input must match your work’s schema. Littleworks hosts the endpoint; your agent still needs to build and place the frontend using the appropriate theme or storefront tools.

Decide what a public request may do

For example, accepting a verified-purchase review requires server-side validation of a purchase-linked invitation. A public endpoint and a customer-supplied order ID alone do not establish eligibility. Never put an agent token in storefront code.

Return JSON

Return a JSON-compatible value or Response.json(...) with a status. Littleworks forwards the body and status, not arbitrary headers, cookies, streaming output, or HTML. This is an API endpoint, not a frontend hosting service.

Handle traffic protection

Littleworks automatically applies burst limits and store execution budgets. A throttled request receives HTTP 429 with Retry-After and error.retryAt. Back off; do not automatically replay a mutation. The Shopify admin shows affected works and retry guidance. These limits are platform policy, not merchant settings.