CAPS

Caps V3 Rest API

CAPS® Complete Transition to
CAPS® V3 REST API

CAPS is upgrading our infrastructure to provide a faster, more secure connection for our partners. We are moving away from the SOAP v2 API in favour of our high-performance REST v3 API.

Our legacy SOAP v2 API will be retired on 27th July, 2027. To ensure business continuity without interruption, please have your developers begin the migration process now.

Key Benefits

This transition optimises our platform for:
  • Improved Stability by adopting the latest technology standards
  • Faster Updates by streamlining our code base to release new features more quickly
  • New Features by prioritising innovations and enhanced claims workflows

Support
Resources:

As part of our commitment to our partners, there will be comprehensive documentation and dedicated technical assistance throughout the 18-month window. Please reach out to our CAPS® team to discuss any migration details.

What is happening?
CAPS® is formally decommissioning the legacy SOAP API and migrating all systems to the modern REST API on 27th July, 2027. To help you plan accordingly we are providing an 18-month notice period to provide you with enough time to get the migration project road mapped and built. To ensure you maintain connectivity and business continuity to CAPS®, the team will provide support to help you with the migration throughout this period.
  • SOAP-based integrations are becoming harder to maintain and evolve.
  • REST v3 is already live and proven.
  • Future CAPS® innovations will only be delivered on v3.
  • Delaying would limit our ability to innovate and support partners long term.
  • Seamless, two-way data sharing
  • Unique claim handling
  • Two-way parts information
  • Enhanced estimate and invoicing data
  • Real-time error feedback
  • Improved recovery workflows
  • A more modern API aligned with industry standards
Partners must:
  • Plan and execute migration from SOAP v2 to REST v3
  • Begin migration as early as possible within the 18-month window
  • Engage with CAPS® support and documentation to ensure a smooth transition
Please note: Failure to migrate before the sunset date will result in loss of service.
CAPS is committing to:
  • 18 months’ formal notice
  • A dedicated CAPS® migration information page on the website
  • Virtual office hours
  • Proactive account and support outreach
  • A high-priority support channel during the final countdown
Please note: This is a supported transition, not a “drop and run”
If a partner does not migrate:
  • Their SOAP v2 connection will stop working at sunset (27th July, 2027)
  • Their services (and their customers’ workflows) will be disrupted
  • CAPS® will not extend the deadline beyond the communicated sunset date
Scroll to Top