We've updated the UI for custom components in the API Developer Portal. Components including Callouts, Card/Card Group, Accordion/Accordion Group, Frame Image, Frame Video, Mermaid, and Table have been updated with a cleaner, more polished look — making your documentation feel more cohesive and professional.
This release enhances SDK documentation title generation from your OpenAPI specifications. We now apply smarter casing rules to endpoint titles and model names. You'll see improved handling of prepositions, acronyms, and any words you've defined in the DoNotSplitWords list.
We've introduced success notifications for API calls in API Recipes, allowing developers to confirm a successful response directly in the workflow.
A new ConfigureComponentSorting codegen setting is now available, providing independent sorting control for each API component type in generated SDK docs and API Portals.
We’ve enhanced the overall usability and accessibility of the API portal, making it faster to navigate and easier to consume across different workflows.
This release enhances SDK documentation title generation from your OpenAPI specifications. We now apply smarter casing rules to endpoint titles and model names. You'll see improved handling of prepositions, acronyms, and any words you've defined in the DoNotSplitWords list.
Enhanced SDK documentation for enumeration casing across all supported languages. This update ensures consistent and accurate environment enumeration representation in the Getting Started section for all languages. We also improved enum casing in the model documentation section for Java.
We've enhanced SDK documentation completeness and alignment with the actual implementation for Java, .NET, and Go SDKs. This update includes model documentation for parameter collection classes and updated endpoint documentation that presents collected parameters as unified model references, resulting in clearer and more accurate SDK documentation.
We have improved error handling in PHP, TypeScript, Java, .NET, and Go code samples to make it clearer, more consistent, and easier to handle typed errors, while still exposing response metadata like status codes and headers.
We've moved the API playground and code samples into a drawer interface that opens on demand. This reduces clutter on endpoint pages, particularly for endpoints with deeply nested fields, and keeps documentation visible while developers explore your API.