RevDesk
  • Pricing
Product
Features
AI Coworkers
AI coworkers that do the work, not just answer questions.
Omnichannel Messaging
iMessage, WhatsApp, SMS, and email with shared context.
Coaching & Enablement
Coach reps while the call is still happening.
CRM & Desk
A CRM that updates itself and shows what happens next.
Tools
RevDesk API & MCP
Connect your systems and build with RevDesk.
Voice AI
Answer every call and work every lead.
Follow-Up & Reactivation
Follow up until the customer answers.
Desking & Deal OperationsDealerships
Send deals without leaving RevDesk.
Managed PipelineManaged service
RevDesk runs approved outreach for you.
Reporting & Insights
See what is happening across every store.
Solutions
Industries
Automotive
Work every internet lead like your best BDC
HealthcareHIPAA
Patient outreach, intake, and follow-through
Law Firms
Intake, conflict screening, booked consults
B2B SaaS
Speed-to-lead, trials, and partner links
Home Services
Book more jobs from every call and get more customers
Logistics
Cover loads and carriers around the clock
AI Coworkers
Speed-to-Lead
Calls new form leads in seconds
Outbound SDR
Works your lists, warms, books
Customer Care
Reviews, referrals, follow-up care
Re-Engage
Wins back dormant pipeline
ReceptionistIncluded
Answers and routes every call, on every plan
Resources
Blog
Field notes from useful AI
Changelog
What’s new in RevDesk
Developers
RevDesk API, SDK, CLI, webhooks, and MCP
Docs
Platform documentation
Case studies
Stories from leading customers
Trust Center
Security, privacy, and eligible BAAs
Pricing
Sign InBook a Demo
Sign InBook a Demo
RevDesk developers

Version confidence

RevDesk developer changelog

Track RevDesk API, SDK, CLI, MCP, schema, and deprecation changes through public versioned release and policy surfaces.

What it is

RevDesk versions its public REST API in the URL and publishes its application, SDK, CLI, and MCP artifacts through versioned release surfaces. Integrators should pin package versions, monitor release notes, and follow the published versioning and deprecation policy before changing production clients. Deprecation is documented with a migration path and timeline rather than silently changing a stable v1 operation.

When to use RevDesk developer changelog

  • Evaluate whether an API, SDK, CLI, or MCP upgrade changes an integration.
  • Find a migration path and support window for a deprecated operation.
  • Verify which package or MCP server version is currently published.

Recommended workflow

  1. 1Monitor the public RevDesk changelog and the release feed for the artifact you use.
  2. 2Compare the released OpenAPI contract and package version in a test environment.
  3. 3Adopt the documented replacement before the published sunset date.

Safety and approval boundaries

  • Do not infer compatibility from an unversioned marketing announcement.
  • A deprecated operation remains documented until its announced sunset; removal must follow the public policy.
  • Production clients should pin and deliberately upgrade SDK or CLI versions.

Official RevDesk resources

RevDesk product changelogCustomer-facing shipped product changes.API versioning and deprecationVersion identifiers, deprecation signals, migration, and sunset policy.@revdesk/sdk versionsPublished SDK and CLI release history.RevDesk SDK releasesSource releases and release notes.

Canonical page: https://www.revdesk.com/developers/changelog

RevDesk
Product
AI CoworkersOmnichannel MessagingCRM & DeskCoaching & EnablementReporting & InsightsVoice AIFollow-Up & ReactivationPricingBook a Demo
Solutions
For AutomotiveFor HealthcareFor Law FirmsFor B2B SaaSFor Home ServicesFor Logistics
Resources
BlogDevelopersDocumentationChangelogRoadmapSMS SubscribeCase StudiesAffiliate
Company
AboutCareersPartnersBrandContactSecurityTrustStatus

Ask your AI assistant about RevDesk

revdesk.com/llms.txt
© RevDesk™ 2026 · Cell Labs, Inc.Privacy Policy·Terms of Service·Acceptable Use·Sub-processorsRevDesk™ is a trademark of Cell Labs, Inc. All other marks are property of their respective owners.