Skip to main content

​
Changelog

​
Versioning

The Journeybee API is versioned via the URL path (/v1/). Breaking changes will only be introduced in new major versions. Non-breaking additions (new fields, new endpoints) may be added to the current version at any time.

​
v1.3.0

​
Audit Log

  • Audit Log — GET /v1/audit-log returns a unified, company-scoped activity feed across leads, deals and partnerships. Each entry carries the entity, action (created / updated / deleted / archived / restored), a rendered actor label, and a changes array describing what changed.
  • Expanded field coverage — audit entries now track many more fields per entity:
    • Partners — name, email, phone, website, description, partner type, offline flag, accepted/invited dates, country, currency (in addition to tier, category, stage, archive state).
    • Deals — currency and expiration date (in addition to label, value, commission, stage).
    • Leads — rejected reason, direction, campaign and distributor (in addition to contact fields and status).
  • Human-readable values — foreign-key fields resolve to labels rather than ids (stage, tier, category, country, currency, campaign, distributor), deal amounts are formatted in the deal’s currency, and create entries are attributed to the record’s creator.

​
v1.2.0

​
Resources & LMS

  • Resources — Full CRUD with content blocks (text, image, video, document, embed, quiz, and more), tags, categories, and folder organization
  • Certifications — Full CRUD with curriculum management (ordered resources with prerequisites), enrollment tracking, categories, and folders
  • Folders — CRUD for organizing resources and certifications into hierarchical folders

​
Rooms

  • Rooms — Full CRUD for partner portal pages with 16 room types and 14 block types (text, video, action bars, banners, goals, pricing calculators, etc.)
  • Room access control — Manage room visibility via tiers, categories, stages, tags, and direct partnership associations

​
Webhooks

  • Webhook event schemas — Full typed payload documentation for all 16 webhook events (leads, deals, partners, messages) in the API Reference

​
Improvements

  • JSONB fields fully typed — Commission calculations, pricing calculator configs, resource block content, room block settings, and custom field values now show complete structures in the API docs
  • UUID validation — All UUID parameters now validate format (previously accepted any string)
  • Asset company scoping — Asset references now verify company ownership

​
v1.1.0

​
Developer Tools

  • TypeScript SDK — @journeybee/sdk with typed functions for every endpoint. See the SDK guide.
  • MCP Server — Connect Claude and other AI assistants to Journeybee. See the MCP guide.
  • operationId on all endpoints — Every endpoint now has a stable operationId (e.g., listLeads, createPartner) for SDK method names and MCP tool names.

​
New Endpoints

  • Leads — Full CRUD with sub-resources: tags, assigned users, contacts, custom fields, notes, attributions, distributors, products, quotes, tasks
  • Deals — Full CRUD with sub-resources: tags, notes, products, payments, custom fields, commission, tasks
  • Tasks — Full CRUD with assigned users
  • Commissions — Full CRUD with tier/category/partnership scoping
  • Contacts — List and get across partnerships
  • Products — Full CRUD
  • Pricing Calculators — Full CRUD with fields, products, and formulas
  • Attributions — Full CRUD
  • Currencies — List
  • Users — List company team members

​
v1.0.0

Initial release

​
Endpoints

  • Partners — Full CRUD with sub-resources: tags, assigned users, domains, custom fields, contacts, notes, resellers
  • Partner Stages — List, create, update, delete
  • Deal Stages — List, create, update, delete
  • Tiers — List, create, update, delete
  • Categories — List, create, update, delete
  • Tags — List, create, update, delete
  • Custom Fields — List, create, update, delete with option management
  • Custom Field Values — List, create, update, delete

​
Authentication

  • Bearer token and Api-Key authentication
  • Read/write permission model
  • Rate limiting (100 requests/minute)