Read orders and proofs, push warehouse records, and get told when something changes. The scopes are granular on purpose: a WMS integration should not arrive with your customer list attached.
Set up in 5 minutes, no code · Works with Shopify and WooCommerce
Most APIs hand out one key that opens the whole account. Give a warehouse partner access to pallet records and you have handed them orders, buyers and disputes too — with no way to take back just that part.
Seven scopes, granted per key: orders read and write, proofs read and write, warehouse read and write, and webhook management.
Warehouse scopes are their own thing. A WMS integration can push pallet records without ever seeing an order or a buyer.
Each endpoint carries its own secret and its own event subscription, with delivery status and failure count visible to you rather than buried in a log.
Order approved, order disputed, order shipped, proof delivered, dispute resolved, plus two warehouse events — named after what happened, not after which table changed.
Keys show their prefix, last use time and last IP, and can be revoked one at a time. Rotating one integration does not disturb the others.
Failed deliveries are retried and the failure count sits on the endpoint, so a flaky receiver is visible rather than silent.
Name it and tick only the scopes that integration genuinely needs.
Bearer token. The key's prefix and last use are shown back to you in the dashboard.
Register an endpoint and choose which events it should receive.
Check the signature against that endpoint's secret, then do your thing.
Facts, not adjectives. Everything below describes what the product does today — nothing here is on a roadmap.
Availability
API access is included from Business. Warehouse scopes additionally require the Warehouse add-on.
PricingOnly as a hash. You see the full key once, at creation, and a prefix afterwards so you can tell your keys apart in the dashboard.
Yes — that is exactly why warehouse scopes exist separately from order scopes.
Deliveries are retried, and the endpoint's failure count is visible in the dashboard, so you find out it is happening instead of discovering it weeks later.
Yes. Create the new key, move your integration across, then revoke the old one. Keys are independent, so nothing else is affected.
Each part is useful on its own. Together they turn one recording into an answer for every kind of claim.
Set up PallasMark in 5 minutes and turn every order into evidence that wins. No credit card required.