The API Report CardAPI Index
I Heart Jane

I Heart Jane API

Cannabis Dispensary E-Commerce & POS · iheartjane.com

Jane publishes a Swagger-documented REST API for orders, products, inventory, and customer events, plus a TypeScript DM SDK. Access is not self-serve; a Jane account representative must approve API and SDK enablement. No public rate-limit documentation exists.

Last verified: July 2026Retail & Ecommerce
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublic Swagger docs at api.iheartjane.com plus a TypeScript DM SDK with its own documentation site.
AccessPOORAccess to the API and DM SDK requires approval from a Jane account representative; there is no self serve signup.
CoverageGOODREST endpoints cover orders, products, inventory, and customer events, the core dispensary retail objects.
AuthPOORPartner-issued keys handed out after account-rep sign-off; no self-serve credentials or documented OAuth.
Docs & DXGOODA public Swagger UI plus a dedicated TypeScript DM SDK documentation site.
StabilityMIXEDNo public rate-limit documentation; partners coordinate request volume with Jane support around events like 4/20.
MORE FROM THE REPORT CARD
Supergood: I Heart Jane has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

I Heart Jane scores D on the API Report Card. Jane publishes a Swagger-documented REST API for orders, products, inventory, and customer events, plus a TypeScript DM SDK. Access is not self-serve; a Jane account representative must approve API and SDK enablement. No public rate-limit documentation exists.

Tried to integrate with I Heart Jane?
SOURCES
API and DM SDK access gated behind Jane account rep approval, slowing integrator onboarding dm-sdk-docs.iheartjane.com
Documentation fragmented across api.iheartjane.com (Swagger), dm-sdk-docs.iheartjane.com (DM SDK), and partner help-center articles api.iheartjane.com
No public rate-limit documentation; partners report having to coordinate request volume with Jane support during high-traffic events (4/20, holidays) autoscraping.com
Consumer iheartjane.com data accessed by third parties via Algolia/internal endpoints, which Jane actively rate-limits and bot-blocks autoscraping.com
POS-side integrations require coordination between three parties (dispensary, POS vendor, Jane), so debugging order-sync failures is multi-tenant by default support.posabit.com
CRM partners (Alpine IQ, EngagePHD, SpringBig) document multi-step Jane-side enablement and webhook configuration to receive customer/order events support.alpineiq.com
No public partner / certified-integration program comparable to Dutchie's Certified Partner Program - integrations are negotiated 1:1 iheartjane.com
Orders intermittently fail to load into the connected POS, forcing manual re-entry by budtenders g2.com
Slowdowns and partial outages affecting retail operations - including industry-press-covered slowdown event mjbizdaily.com
Pricing not publicly disclosed; dispensaries report contract-renewal price increases and lock-in to bundled Jane Pay / Jane Media softwareadvice.com
Customer support response times degrade during incidents; status page is the primary channel for outage comms status.iheartjane.com
Menu/SKU sync inconsistencies between Jane and the connected POS, especially after promotions / discount changes capterra.com
Reporting / analytics depth lags Dutchie's multi-location consolidated views for MSOs selecthub.com
Embedded menu iframe pattern limits design flexibility vs. fully headless / API-only approach hybridmarketingco.com