← Back to all docs

POSaBIT API

POSaBIT is a cannabis retail point-of-sale, payments, and inventory platform for dispensaries—covering POS, online menus, mobile checkout, loyalty, payment processing, and Metrc track-and-trace compliance. An unofficial API lets you pull inventory, transactions, customers, manifests, coupons, and menu data—and push updates like inventory adjustments, order status, and customer records back into POSaBIT.

By Alex KlarfeldMay 30, 2026
POSaBIT API

What is POSaBIT?

POSaBIT is a cannabis retail point-of-sale and inventory management platform that helps dispensaries optimize compliance, revenue, and customer experience. Retailers use POSaBIT to ring sales, manage inventory, process payments, run omnichannel online menus, and stay compliant with state track-and-trace systems like Metrc—connecting to third-party services through an open API.

Core product areas include:

  • POSaBIT POS (core in-store point-of-sale and checkout)
  • POSaBIT Menus (omnichannel online ordering and digital menus)
  • Pocket POS (mobile, line-busting and delivery checkout)
  • POSaBIT Pay (integrated cannabis payment processing and tipping)
  • Compliance and Metrc track-and-trace integration (Metrc Connect)
  • Loyalty, analytics, and reporting plus partner integrations (Weedmaps, Leafly, Dutchie, Jane, Headset, Springbig)

Common data entities:

  • Inventory items, products, batches, and menu feeds
  • Transactions, sales histories, tills, and incoming orders/quotes
  • Customers, loyalty profiles, and purchase history
  • Manifests and manifest items (transfers and delivery)
  • Coupons, promotions, and discounts
  • Employees/users and terminal tills

The POSaBIT Integration Challenge

Dispensaries run high-volume, heavily regulated workflows on POSaBIT every day, but turning its POS and compliance surfaces into reliable API-driven automation is non-trivial:

  • Versioned API surface: Venue API spans V1/V2/V3 plus a separate Vendor API, with V3 on Basic Auth and V1/V2 on bearer tokens—endpoint coverage and shapes differ by version
  • Per-venue credentials: Access is scoped to each store's venue and tokens, so multi-location operators juggle separate auth contexts per dispensary
  • Compliance coupling: Inventory and transactions are tied to Metrc track-and-trace, so any automation must respect package tags, manifests, and state reporting rules
  • Webhook-driven order flow: Order status updates arrive via callbacks rather than polling, so integrations need reliable callback handling and retry logic
  • Real-time inventory pressure: Menus, online ordering, and in-store checkout all read the same inventory, so freshness and concurrency matter under peak demand
  • Partner ecosystem variability: Data also flows through Weedmaps, Leafly, Dutchie, and other connectors, each with its own sync cadence and field mapping

How Supergood Creates POSaBIT APIs

Supergood works against POSaBIT's POS API and authenticated venue surfaces to deliver a resilient, normalized API layer for every dispensary location—so you integrate once instead of stitching together V1/V2/V3 quirks per store.

  • Handles V3 Basic Auth and V1/V2 bearer tokens with per-venue credentials in a managed session
  • Normalizes inventory, transactions, customers, manifests, and coupons into consistent JSON objects across versions
  • Consumes order-status webhooks and exposes them as clean events with retry and replay handling
  • Respects Metrc-linked compliance fields, package tags, and manifest structures so automation stays audit-clean

Use POSaBIT with AI agents: POSaBIT MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your venues, API versions, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready POSaBIT adapter normalized across your locations and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as POSaBIT evolves.

posabit

API Endpoints

Authentication

POST/authenticate

Authenticate to a POSaBIT venue using V3 Basic Auth or a V1/V2 bearer token and obtain a session for downstream calls.

Inventory

GET/inventory

List inventory items, products, batches, and quantities for a venue with filters for menu, category, and availability.

Inventory

PATCH/inventory

Update inventory quantities, pricing, or availability while preserving Metrc package tags and compliance fields.

Transactions

GET/transactions

Retrieve sales histories and transaction records with line items, totals, payments, and tips by date range.

Customers

GET/customers

Pull customer profiles, loyalty status, and purchase history with search and pagination.

Customers

POST/customers

Create or update a customer record, including loyalty enrollment and contact details.

Compliance

GET/manifests

Retrieve manifests and manifest items for transfers and delivery, linked to Metrc track-and-trace.

Promotions

GET/coupons

List coupons, promotions, and discounts available at a venue with eligibility rules.

Use Cases

Sync inventory and menus across channels

- Pull real-time inventory, products, and batches into a central catalog - Push price and availability updates back to POSaBIT while preserving Metrc package tags - Keep online menus, Pocket POS, and in-store checkout reading the same stock levels

Centralize sales and transaction reporting

- Stream transactions, line items, payments, and tips into BI and accounting tools - Reconcile tills and incoming orders across multiple dispensary locations - Surface daily sales, basket, and category trends without manual exports

Unify customer and loyalty data

- Sync customer profiles, loyalty status, and purchase history into your CRM - Push new enrollments and updates back into POSaBIT - Trigger marketing and retention flows from real-time purchase events

Automate compliance and transfers

- Pull manifests and manifest items tied to Metrc track-and-trace - Validate package tags and quantities against state reporting requirements - Route delivery and transfer events to compliance and logistics systems

Technical Specifications

Authentication

V3 Basic Auth and V1/V2 bearer tokens, scoped per venue, handled in a managed session

Connectivity

POSaBIT POS API (Venue API V1/V2/V3 and Vendor API) plus authenticated venue surfaces

Response format

Normalized JSON across inventory, transactions, customers, manifests, and coupons

Rate limits

Adaptive throttling tuned per venue to avoid POSaBIT-side limits during peak checkout

Session management

Automatic credential rotation and per-venue token refresh across multi-location operators

Data freshness

Near real-time reads for inventory, sales, and customers with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Order-status callbacks surfaced as clean events with retry and replay handling

Latency

Sub-second reads on cached inventory and menus; multi-second writes when posting orders and updates

Throughput

Horizontally scaled workers sized to multi-location, high-volume dispensary traffic

Reliability

Retry, backoff, and idempotency keys for inventory adjustments and order updates

Adaptation

Continuous monitoring of POSaBIT API versions, Metrc Connect changes, and partner integration drift

Frequently asked questions

Yes. Supergood handles per-venue credentials and tokens for each store, then normalizes inventory, transactions, and customer data into a single consistent surface across all your POSaBIT locations.

POSaBIT's Venue API spans V1/V2/V3 (with V3 on Basic Auth and V1/V2 on bearer tokens) plus a separate Vendor API. Supergood abstracts these version and auth differences so you integrate against one normalized contract.

Supergood preserves Metrc-linked fields, package tags, and manifest structures on every read and write, so inventory adjustments and transfers stay aligned with state track-and-trace reporting.

Yes. POSaBIT delivers order-status callbacks via webhooks, and Supergood consumes them, normalizes the events, and adds retry and replay handling so you never miss a status change.

You can read inventory, transactions, customers, manifests, coupons, and menu feeds, and push updates such as inventory adjustments, customer records, and order status back into POSaBIT.

Ready to get a real API?