Jane Technologies API
Jane documents several surfaces: a REST API with public Swagger, Roots headless commerce APIs with checkout webhooks, and a TypeScript DM SDK. Production credentials require Jane's approval, and the docs steer catalog reads to Algolia rather than REST.
Frequently asked questions
Jane Technologies scores D+ on the API Report Card. Jane documents several surfaces: a REST API with public Swagger, Roots headless commerce APIs with checkout webhooks, and a TypeScript DM SDK. Production credentials require Jane's approval, and the docs steer catalog reads to Algolia rather than REST.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Jane Technologies, Inc. (operating as 'Jane', consumer brand iheartjane.com) is a Santa Cruz, California cannabis retail technology company that runs both a consumer-facing marketplace at iheartjane.com and a B2B e-commerce/menu stack that powers dispensary websites and apps.
Vertical SaaS for state-licensed cannabis retail: dispensaries (single-store independents through multi-state operators), cannabis brands that sell into those dispensaries, and end consumers who shop the iheartjane.com marketplace. A dispensary signs a partnership with Jane and gets a hosted menu (Ecommerce or Ecommerce Premium) embedded on its own domain, or builds a fully custom storefront on the Roots headless APIs.
High within cannabis retail, second to Dutchie. Jane publicly cites 2,500+ dispensary and brand customers across 39 US state markets, with an estimated ~3,000 dispensaries on the menu side.
Company: Jane Technologies, Inc.. Founded: 2015. HQ: Santa Cruz, California. Founders: Socrates Rosenfeld (CEO), Abraham Mamerow. Employees: ~150-178 (2026). Reported revenue: ~$120M annual.
Founded in 2015 in Santa Cruz, CA.
Roots, DM SDK and production API access are explicitly gated behind 'approval from Jane' and partner-team onboarding, slowing self-serve integrator adoption. Jane's own docs steer integrators away from the REST API toward Algolia for read traffic ('Algolia is much faster and has much higher usage quotas'), narrowing the third-party REST footprint and making rate limits/auth on REST less battle-tested. Full sourced list under Sources below.
Common alternatives include Dutchie, Weedmaps, Leafly, Meadow, Flowhub, Treez. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.