For the technical

Developers and API

Wenmar Pro has a full JSON API. Anything the CLI can do, your own code can do too. There are three ways in.

JSON API

Every shop screen is also an API endpoint. Add .json to the same URL.
Authenticate with a Bearer token from Settings, then API Tokens.
Responses are plain JSON with no wrappers or envelopes.
Pagination uses the standard Link header.

# Same URL as the screen, plus .json
curl "https://app.wenmarpro.com/<any screen>.json" \
  -H "Authorization: Bearer $WENMAR_TOKEN"

SDKs

Go

Retries, pagination and HTTP caching built in.

go get github.com/wenmar-pro/wenmar-sdk/go

Ruby

The same behaviour, built on Faraday.

gem install wenmar

Command-line tool

For shop owners who prefer the terminal, and for AI agents. Output is a readable table by default. Add --json, --agent or --jq for machine-readable output.

macOS and Linux

brew install --cask wenmar-pro/tap/wenmar

curl -fsSL https://raw.githubusercontent.com/wenmar-pro/wenmar-cli/main/install-cli | bash

Windows

scoop bucket add wenmar https://github.com/wenmar-pro/scoop-bucket
scoop install wenmar

github.com/wenmar-pro/wenmar-cli

Hermes and OpenClaw

Wenmar Pro works with Hermes and OpenClaw. Step-by-step guides for connecting them are on the way. Until then, email ben@wenmarpro.com and he'll help you get set up.

Getting a token

Create tokens in the web app under Settings, then API Tokens. Each token is scoped to one location, can expire, and can be revoked any time.

Using API tokens

License

SDK and CLI code is MIT licensed. The API docs are CC BY-SA 4.0.