Partner API · v1

BakedBot Developer API

Connect your cannabis POS or e-commerce platform to BakedBot's retention and loyalty engine. Send completed transactions, enroll customers, look up loyalty profiles, and run compliance checks — all over a REST API secured with org-scoped API keys.

Base URL
bakedbot.ai
Version
v1
Auth
Bearer token
Format
JSON

What you can build

The BakedBot API is designed for cannabis POS and e-commerce platforms. Here are the most common integration patterns.

Transaction webhook

Fire a POST on every completed sale. BakedBot awards points, closes the loyalty session, and queues retention campaigns automatically.

Checkout loyalty lookup

Customers tap their phone number at checkout. Look up their points, tier, and active rewards in real time to apply discounts.

Automated campaigns

Transaction data feeds BakedBot's segmentation engine. Lapsed customers, loyalty milestones, and product replenishment triggers fire without manual setup.

Compliance at the source

Run any promotional copy through Deebo before displaying it — state-level cannabis advertising rules, checked in under 500ms.

API endpoints

All endpoints are under https://bakedbot.ai/api/v1. Each requires a Bearer token with the listed permission scope.

POST
/api/v1/integrations/pos/transactions/completed

Record a completed POS transaction

Award loyalty points and trigger retention campaigns when a sale closes.

write:transactions
POST
/api/v1/loyalty/members

Enroll a customer in loyalty

Create a loyalty member and return a QR pass for immediate use at checkout.

write:members
GET
/api/v1/loyalty/members/lookup

Look up a loyalty profile

Retrieve points balance, tier, rewards, and pass details by phone or member ID.

read:customers
POST
/api/v1/compliance/check

Check content for compliance violations

Validate promotional copy against cannabis advertising rules before display.

compliance:check

Authentication

Every request must include an Authorization header with a Bearer token issued by BakedBot.

Keys are scoped per organization and per permission. A key issued for one dispensary cannot read or write data for another. Keys are provisioned by the BakedBot team during onboarding.

Request API access →

Authorization: Bearer bb_live_<your_key>

# Example: record a completed transaction
curl -X POST https://bakedbot.ai/api/v1/integrations/pos/transactions/completed \
  -H "Authorization: Bearer bb_live_abc123" \
  -H "Content-Type: application/json" \
  -d '{
    "organizationId": "org_your_dispensary",
    "posTransactionRef": "txn_98765",
    "totalCents": 8500,
    "subtotalCents": 8500
  }'

Interactive reference

Full request and response schemas with live examples. Use the sidebar to jump to any endpoint.

Ready to integrate?

Contact the BakedBot team to get an org-scoped API key. We'll walk you through the onboarding flow and have your first transaction flowing within a day.