Abdul Hannan Shaikh September 10, 2025

This month, we're doubling down on what matters most: turning your API documentation into a strategic asset that drives real business outcomes. We've enhanced our DX Analytics to give you deeper visibility into how developers actually engage with your APIs, plus we're cooking up something exciting that could transform how your team approaches API integration challenges.

Highlights include our proven DX Analytics capabilities, our VS Code Extension reaching 4,000 installations, and ongoing development in AI-powered context generation.

📊 DX Analytics - Your API's Success Story, Data-Driven

Finally, Analytics That Actually Matter for API Leaders

Remember when measuring developer experience meant guessing based on support ticket volume? Those days are behind us.

DX Analytics gives you the numbers that actually matter. While your competitors are still guessing why developers aren't adopting their APIs, you'll know exactly where yours are succeeding—and where they're hitting walls.

The game-changer? Finally having the data to back up your developer experience investments. When leadership questions the documentation budget, you can show them the direct line from portal improvements to API adoption.

What This Changes for Your Team

  • Skip the "Is our docs working?" guessing game: Transform vague developer feedback into concrete metrics that guide your next quarter's priorities
  • Developer onboarding friction gets surgical precision: Instead of "our docs need work," you get "developers drop off at step 3 of authentication"
  • Engineering and marketing finally speak the same language: Share metrics that both teams care about—adoption rates, engagement patterns, and conversion funnels
  • Support team becomes proactive instead of reactive: Spot friction points before they become support ticket avalanches

The latest improvements include enhanced user tracking that captures more nuanced developer behaviours, giving you the granular insights needed to optimise every touchpoint in the developer journey.

Ready to see how DX Analytics can transform your API strategy? Connect with our team to get started.

🛠️ 4,000 installations and counting: Why Developers choose our OpenAPI validation tools 

Our VS Code Extension just crossed 4,000 installations, with growing adoption among enterprise API teams managing complex specifications.

"The extension is working great on big spec files (~100k lines) with lots of references. The default rulesets cover different types of validations, and it's great at pinpointing possible issues that might be hard to detect otherwise."   — Senior Consulting Engineer, Juniper Mist

Here's why enterprise teams are adopting our validation tools:

  • Built for massive scale: Handle hundreds of specs across dozens of teams, processing files with hundreds of thousands of lines without performance degradation.
  • Enterprise workflow integration: Seamlessly fit into your development process through VS Code for developers and GitHub App for CI/CD pipelines. 
  • Reduce enterprise compliance risk: Catch OpenAPI specification issues before they become customer support headaches.

Curious to see what you're missing in your OpenAPI validation workflow? Check out our VS Code Extension to spot issues you didn't know existed, or use our GitHub App to catch problems as soon as they are committed to your GitHub repo.

🔬 What We're Working On: AI Context That Changes Everything

The Integration Challenge Every API Team Faces

You know the story: developers find your API, get excited, then hit the inevitable wall of complex authentication flows and scattered documentation. Most give up. The few who persist spend days on what should take minutes.

We're working on something that could flip this entire dynamic. See it in action!

The developer went from zero to a working dashboard without diving into documentation rabbit holes, without authentication headaches and without the usual integration friction that kills momentum.

🛠 Improvements

Proxy configuration support added to Python, Java, and Ruby SDKs

We've added support for configuring proxy servers in our Python, Java, and Ruby SDKs. This enhancement enables API requests to be routed through custom proxy servers.

The SDKs provide a very simple interface for proxy configuration - developers can set proxy settings during SDK client initialisation, configuring address, port, username, and password as needed for their specific network environment.

🔗 See our proxy configuration feature documentation for details.

Removed javax dependencies for Java SDKs

We've eliminated transitive javax.* dependencies from the apimatic/core package to improve compatibility across different Java environments.

This change prevents conflicts in newer Java environments while maintaining support for Java 8 and above. Instead of migrating to jakarta.* namespaces, we've refactored the library to rely on functionality provided by Jackson, removing the need for javax.* APIs altogether.

This improvement ensures your Java SDKs work seamlessly across a broader range of Java versions and environments without compatibility issues.

🔗 See the changelog for details.

⚠️ Upcoming Changes

TypeScript Module Export Changes (Effective November 1st, 2025)

Important: This is a pre-release notice for changes that have not been released yet.

We're updating how we export modules in TypeScript SDKs to align with modern TypeScript best practices and improve compatibility across different environments.

These upcoming changes will:

  • Reduce bundle size for browser applications
  • Improve import clarity with more explicit patterns
  • Catch errors at compile time rather than runtime for ESM users
  • Enhance compatibility between browser and Node.js environments

What's changing?

  • Adding a new exports field in package.json
  • Updating internal imports to use the .js extension

Do you need to take action?

If you follow TypeScript best practices and the import patterns shown in our SDK documentation, no changes are required. However, if you use certain unconventional patterns (default imports in Node.js ESM or deep imports in CommonJS), you'll need to update your code.

🔗 See our pre-release notice for details.

📢 Your Voice Shapes What We Build

Your feedback makes our product better.

  • 🐞 Found a bug? Report it at support@apimatic.io and earn eternal developer karma
  • 💡 Got a brilliant idea? Schedule a 15-minute chat and share it before our product team claims they thought of it first. 
  • 🎉 Love something we built? Tell us so we can argue less about what to build next

Follow us on LinkedIn to stay updated with the latest news from APIMatic!