CCH Axcess™ Finally Has a Key Just for Vendors: The Designated Vendor Integrator Key

On September 14, Wolters Kluwer announced the Designated Vendor Integrator Key: a dedicated credential for third-party technologies connecting to the CCH Axcess™ API, separate from the key that runs everything else in the firm.

That sounds small. For anyone who has built on the Axcess API, it isn't.

The contractor problem

CCH Axcess™ doesn't offer a sandbox environment, and neither does most other practice management software. Every integration is built and tested against the firm's live database.

Think of it as the contractor problem. Would you hand someone fixing your kitchen the master code to your house, or a temporary code that stops working the moment the job is done? For years, CCH Axcess™ only had the master code to give. A vendor building an integration used the same credential the firm used for everything, with the same reach.

What a dedicated key changes

The announcement is careful in its wording. The key gives firms a way to identify, authorize, and govern each integration on its own, and it separates a vendor's API activity from the firm's own. Here is what that makes possible in practice:

• Scoped access. With its own credential, a vendor's key can be limited to what the project needs, so production data outside the project stays untouched. How finely a firm can scope it will depend on what Wolters Kluwer exposes, and the announcement doesn't spell that out yet.
• A clean cutoff. When development is done, the firm retires the vendor's key. Nothing else in the firm has to change, because nothing else was using it.
• Separate visibility. Vendor calls no longer blend into the firm's own API usage, so the firm can see what an integration is doing and when.

None of this is a feature the firm has to buy. It is basic credential hygiene, and it has been missing from the platform until now.

What to do with it

If your firm has a vendor building on Axcess today, ask whether the work is running on a firm-wide credential. If it is, moving it onto a designated key is the first thing to do.

If you are planning an integration, this is one less reason to hesitate. See what we build on the CCH Axcess™ API, or book a discovery call to talk through your project.