This month, APIMatic’s API Portals got easier to navigate and faster to recover from auth errors: there is more fine grained control over the content hierarchy, the API console auto-focuses on the authentication section after 401 errors, and every Portal ships with a more accessible layout.
On the SDK front, Java, .NET, and Go SDK Docs now document collected parameters as a single input model, and environment enums are documented more consistently across languages.
Here's everything that shipped in February 2026.
This month brings four improvements to your API Portal experience, making documentation easier to navigate and more accessible.
When APIMatic’s default endpoint grouping doesn't match how you want to organize your APIs in the Portal, you can override the default hierarchy with a single toc.yml entry. Reference a group by name using from: endpoint-group and the sidebar pulls in every endpoint that belongs to it, including ones you add later.
The new ConfigureComponentSorting setting lets you set sort order — alphabetical, by HTTP method, or none — independently for endpoints, models, webhooks, and callbacks. This is useful for large APIs where consistent ordering across regenerations matters.
When an API call returns a 401 Unauthorized, the authentication section expands automatically and focuses the first credential field — so developers can correct and retry right away.
This works out of the box on hosted portals after next publish and is enabled by default for Docs as Code deployments.
All portals now ship with a more compact layout that reduces how far developers need to scroll to reach endpoint details and response schemas. Focus states are visually clearer, keyboard navigation is more complete, and screen reader compatibility is improved throughout.
Developers reading your Java, .NET, and Go SDK READMEs see a single named input model for SDK methods with long parameter lists.
When an endpoint groups multiple inputs into a single object, your SDK reflects that with a dedicated class. Now the README does too. The endpoint section shows the collected input as a unified reference like input: CreateUserProfileInput, and the model documentation section includes a dedicated entry for that class.
🔗 See the Changelog for details.
Enum values in the SDK Docs align more closely with enum definitions in the SDKs.
The corrected values will appear in your next SDK regeneration. For most teams this is a documentation-only improvement.
|
Section |
What changed |
|---|---|
|
Getting Started (all languages) |
Environment enum values reflect correct casing |
|
Model documentation (Java) |
Enum fields reflect correct casing |
🔗 See the Changelog for details.
Title Casing Standardization for Endpoint and Model Names in SDK Docs (action required)
Endpoint titles and model names in SDK Docs will update to handle acronyms and prepositions correctly. This applies across all API Portals.
The updated title casing implementation produces cleaner, more consistent headings — for example, acronyms like OAuth stay uppercase rather than being treated as regular words, and prepositions like "of" or "for" are no longer capitalized mid-title.
For most teams this is a visual improvement with no functional impact. However, if any documentation tooling, internal wikis, or scripts reference these heading strings directly (for example, anchor links or automated doc tests), verify they still resolve correctly after regenerating.
🔗 See the Changelog for details.
Updates to the Sdk Generate CLI Command (action required)
The apimatic sdk generate command is replacing the --spec flag with --input, and the default input path is changing.
The change aligns SDK and Portal generation commands so both use identical inputs, simplifying CI/CD pipelines that run both commands. The new --input flag points to the parent directory containing the src folder, rather than the spec directory itself.
🔗 See the Changelog for details.
Your feedback makes our product better.
Reach our support team at support@apimatic.io