Operational contract
The website continues to expose the verified inventory, procurement, receiving, reservation, allocation, transfer, stocktake, fulfilment, return and product-link contract.
STONEWARE DEVELOPER CENTER
API coverage & source sync.
See exactly what the Stoneware website publishes as a supported integration contract, what was checked in the application sources, and what remains an application capability rather than a public API.
VERIFIED
/api/slab/v1/operations41 read collections 79 mutations 163 HTTP operations Public contract status: synchronized Unverified endpoints promoted: 0
PUBLISHED CONTRACT
The public operational API remains 41 reads, 79 mutations and 163 HTTP operations.
The current website reference matches the verified Stoneware operational contract. This release does not invent aliases or promote authenticated application routes as public APIs.
41read collections
79mutations
163HTTP operations
0unverified endpoints added
Canonical compatibility base
/api/slab/v1/operations remains the verified technical base path. The website does not publish a fictional /api/stoneware/v1 alias.
SOURCE AUDIT
Application routes were checked before expanding the website reference.
The audit separates public integration endpoints from internal authenticated web routes so the Developer Center only promises interfaces that are actually supported.
CRMPro 5.0.1
The uploaded CRMPro route provider registers its module route file with the web middleware. Its accounts, contacts, leads, opportunities, quotes, activities and administration routes are application routes, not a public operational API.
Worksuite 6.0.17 core
The uploaded core routes/api.php contains the purchased-module utility endpoint. It does not create a new Stoneware customer, invoice, CRM or accounting API contract.
CAPABILITY BOUNDARY
Product capability does not automatically mean public API.
Stoneware can present richer application experiences than the current public server-to-server integration contract exposes.
ARIDocumented as permission-aware application intelligence. No ARI write API is published without a verified endpoint.
Supplier Finance & FXDocumented as application capability. Finance write endpoints are not inferred from product screens.
CRM & customersAuthenticated CRMPro application routes are not re-labelled as public APIs.
Invoices & accountingCore commercial/accounting actions remain outside this operational API unless explicitly added to a verified contract.
SYNC POLICY
Only verified source changes can expand the Developer Center.
Future Stoneware API updates should follow the same gate: inspect the authoritative route/contract source, identify the authentication and permission boundary, update the endpoint registry, regenerate reference pages, then run count and link assertions before publication.
01Inspect sourceRoutes, controllers and packaged contract.
→02Classify boundaryPublic API vs authenticated application route.
→03Update registryMethods, paths, scopes and fields.
→04Regenerate docsReference, examples and search.
→05Assert coverageCounts, links and non-invention guards.