April '26 Highlights: Add Custom Code to SDKs, Create API Portals Using AI Agents, and Publish SDKs From the APIMatic CLI

April saw a major wave of updates for our platform.
The latest release introduces the ability to inject custom logic, helper methods, and entire files to any APIMatic-generated SDK without losing them during regeneration. We have also launched APIMatic Skills, providing an agent-native way to manage your developer portal via natural language prompts. Additionally, SDK publishing is now integrated into the CLI for seamless CI automation, complemented by several portal usability enhancements.

Here's everything that shipped in April 2026:

🚀Customize generated SDKs without losing your changes on regeneration

You can now add custom logic, helper methods, signature verification, and entire files to any APIMatic-generated SDK, and those changes survive regeneration.

APIMatic-generated SDKs have always been customizable through codegen settings, which let you tune naming conventions, project structure, dependencies, and dozens of other generation options. This release extends that customization model significantly.

You can now treat the generated SDK like your own handwritten code. Add a webhook signature verifier. Wire in a custom auth flow. Bring in an internal logging library. Add a helper method that wraps three endpoints into one call. Inject lifecycle hooks before a request fires or after a response returns.

Regenerate as often as you want; your changes come back exactly as you made them.

How it works

The CLI keeps a git-based source tree inside your build directory with two branches: a main branch holding the latest generated SDK, and a custom branch holding your modifications. You edit the SDK locally as you normally would. When you're ready, you confirm and save your changes; the CLI captures the exact diff. On the next regeneration, those changes are reapplied automatically on top of the freshly generated code.

A typical flow looks like this:

# Generate the SDK with change tracking enabled
apimatic sdk generate --language=typescript --track-changes

# Make your edits in ./sdks/typescript (custom auth, helpers, 
new files, anything)

# Save your customizations
apimatic sdk generate --language=typescript --track-changes

# Later, regenerate after a spec change — your edits come back 
automatically
apimatic sdk generate --language=typescript

From new files to lifecycle hooks, add anything you want to the SDK

• Add new files and directories with custom helpers, utilities, or whole subsystems
• Modify generated files to change auth flows, request handling, or response parsing
• Add hand-written methods to the public SDK interface
• Bring in third-party libraries or swap a generated HTTP client for your own
• Inject lifecycle logic at SDK initialization, before requests, on success, or on errors
• Add custom documentation to your SDK README or inline comments

adding custom code to SDKs

🚀 Build, configure, and ship a developer portal without leaving your AI assistant

You can now describe what you want APIMatic to do, and Claude Code, Cursor, or Codex will run the right CLI commands, edit the configuration, and give you the exact outcome you ask for — guided by APIMatic Skills. If you can describe it, you can do it.

Opinionated setup, no context-switching

Setting up a developer portal involves a long sequence of small decisions: scaffolding a project, wiring up themes, configuring API Copilot, creating API recipes, tuning SEO, and setting up CI/CD.

Every one of those tasks has a "right way" we've documented across our product. APIMatic Skills package that know-how into reusable instruction sets that AI coding assistants load automatically when they detect a matching task. You get guided, opinionated setup without leaving your AI assistant.

From local development to production release with one Skill

Our apimatic-portal skill covers the full lifecycle of building APIMatic Docs as Code portals. Supported in Claude Code, Cursor, and any AI tool that supports skills.

• Authentication: browser-based login, API key fallback, and CI-friendly auth via environment variables
• Project setup: first-time scaffolding then ongoing development via a local dev server with hot reloading
• Theming and branding: colors, fonts, logos, favicons, headers, footers
• Navigation: site structure, nav groups, versioned portals
• API Copilot: configure the in-portal AI assistant and tune its behavior
• SEO and LLMs: generate llms.txt files and configure SEO metadata
• Custom content: guides, custom landing pages, and API recipes (Arazzo workflows)
• Context plugins: set up integrations for coding assistants
• Dynamic configuration: environment-aware portal builds
• CI/CD: setup automation workflows for production builds in CI/CD pipelines

Install with one command

npx skills add apimatic/skills --skill apimatic-portal

Five prompts to try

Here are a few prompts you can try after setting up the skill:

• "Set up an APIMatic developer portal for this OpenAPI spec and start a local dev server."
• "Change the portal's primary color to #1E40AF and set the header logo to ./logo.svg."
• "Add an API recipe called 'Create and Pay an Invoice' for a three-step payment workflow."
• "Generate a GitHub Actions workflow that builds the portal on push and deploys to GitHub Pages."

apimatic-portal skill documentation reference

🚀 Automate SDK publishing using the APIMatic CLI

You can now publish your SDKs and inspect your publishing profiles from a CI pipeline, a release script, or any terminal. Your existing publishing profiles work as-is; the CLI is a wrapper around the same configuration you already manage in the APIMatic dashboard.

For teams running release workflows in Jenkins, Harness, GitHub Actions, or any CI tool that can't drive a browser, this closes the last manual step in the SDK release pipeline. Spec validation, generation, customization reapplication, and publishing now all run from one automated flow.

Five release-pipeline controls

• Trigger publishing via an existing publishing profile straight from a release script
• List every publishing profile on your account so you know which ones are wired where
• Filter by language to publish a single SDK without touching the others
• Preview before publishing with --dry-run to see exactly what will go out
• Skip selected targets with --publish-type, select whether you want to publish SDK source code or an SDK package, or both.

Credentials and registry configuration stay in the dashboard, so secrets never end up in your CI config files.

@apimatic/cli package on npm and check out our changelog.

🛠 Minor improvements

Choose where Try It Out is available in your Developer Portal. Leave it enabled for sandbox and staging where developers should experiment, and turn it off for production environments where your docs page shouldn't be a path to live API calls. The setting is per environment in your Server Configuration, so the rest of the API reference renders unchanged. See the property reference.

Give your portal navigation more room to breathe. Portals with long endpoint names or deeply nested resource groups can now use a wider sidebar so labels read cleanly without truncation. Four predefined sizes are available; pick the one that fits your information architecture. See the changelog entry.