Skip to main content
Early access versionThe 2026-06-unstable schema is an early preview and may still receive breaking changes before the first stable version.
Questions or feedback? Get in touch with our support →

Build integrations with Pickware ERP.

The Pickware ERP GraphQL API gives integrations the same data and operations Pickware uses itself. Feed ERP data into reporting tools, push purchase orders from a procurement tool, or hand off picks to a custom fulfillment layer.

POST /api/graphql/2026-06-unstableschema 2026-06-unstableGraphQL over HTTPS
ERP
stock, purchasing, warehouses
R/W
read and write workflows
13
documented resource areas
scoped
explicit access capabilities

why the api works well for integrations

Designed for integrations merchants depend on.

Four properties matter once an integration is wired into the merchant’s daily ERP operations.

Generated from the schema

The reference is generated from the GraphQL schema, so fields, inputs, and mutations stay close to the implementation.

Built for synchronization

Cursor pagination and filters make it practical to build recurring imports, exports, and background jobs.

Explicit access scopes

Queries and mutations document the read or write scopes a token needs before an integration calls them.

Friendly to LLM agents

The typed schema, explicit field selection, and per-field access scopes give LLM-driven agents a much narrower surface to reason about than a sprawling REST API.

current schema scope

Read everything in the ERP. Write to the operations integrations actually need.

The 2026-06-unstable schema covers the ERP operations integrations reach for most often — read across the model, write to the specific paths listed on the right.

Read

Products, orders, documents, suppliers, supplier orders, goods receipts, batches, warehouses, bin locations, stock, warehouse stock, currencies, and tags.

Write

Stock corrections and transfers, supplier orders and line items, product-supplier configurations, goods receipts, warehouses, bin locations, and complete order shipment.

Stability

2026-06-unstable is an early preview — breaking changes can still land before the first stable schema is released. Future versions ship as separate date-versioned references so integrations can keep using the version they were built against.