v6.6.66

What's Changed

Bug Fixes

• api-responses-document: Fixed gRPC method response not being rendered in the documentation tab. The component now renders gRPC method responses and correctly handles gRPC endpoint detection when statusCode is absent.

Updated Components

Component	From	To
@api-components/api-responses-document	4.2.6	4.2.7

Related Issues

• W-22299818: [APIC] gRPC method response not rendered in documentation tab

Links

• npm: https://www.npmjs.com/package/api-console/v/6.6.66

v6.6.65

Merge pull request #903 from mulesoft/build/6.6.65

Release v6.6.65

v6.6.64

Merge pull request #901 from mulesoft/build/6.6.64

@W-22440070 chore: bump version to 6.6.64

v6.6.63

What's Changed

Bug Fixes

• api-summary: Fixed gRPC navigation when clicking on nested <span> elements inside
  links — the click handler now walks up composedPath() to find the correct element with
  data-id and data-shape-type attributes.
• api-type-document: Fixed dark mode styling for union/oneOf/anyOf toggle buttons —
  background and text color fallbacks were changed to transparent/inherit to avoid
  white-on-white rendering.

Updated Components

Component	From	To
@api-components/api-summary	4.6.18	4.6.19
@api-components/api-type-document	4.2.42	4.2.43

v6.6.62

Fixed

Deep allOf Schema Rendering (Sev 1)

Fixed critical issue where properties from deeply nested allOf schemas (4+ levels) were not rendered in documentation and examples.

Impact: Signature account affected - Missing critical fields in Product Order API documentation.

Root Cause: ExampleGenerator and ApiTypeDocument only performed single-pass iteration through allOf shapes, missing properties in nested inheritance chains.

Solution: Added recursive property collection with depth limiting and circular reference detection.

Updated Components

• @api-components/api-example-generator: 4.4.35 → 4.4.36
• @api-components/api-type-document: 4.2.41 → 4.2.42

Related Issues

• W-21368901: Deep allOf (4+ levels) not rendering properties

Release 6.6.61

Release Date: March 2, 2026

Bug Fixes:

gRPC Service Method Names (https://gus.my.salesforce.com/a07EE00002V3YhdYAF)

Fixed missing method names in Summary view and Navigation menu for gRPC APIs with multiple methods. Previously showed only "UNARY" labels without method identification.

gRPC Message Type Names (https://gus.my.salesforce.com/a07EE00002V40oGYAR)

Fixed "Unnamed type" display for gRPC messages defined with oneof. Now shows actual message type names.

Updated Components

• @api-components/api-navigation: 4.3.21 → 4.3.22
• @api-components/api-summary: 4.6.17 → 4.6.18
• @api-components/api-type-document: → 4.2.41

Links

• npm: https://www.npmjs.com/package/api-console/v/6.6.61

v6.6.60

Bug fixes

Fix: Examples not displaying in Exchange for OAS 3.0.1 requestBodies with allOf inheritance

Fixed an issue where examples defined under requestBodies with inherited properties via allOf in OpenAPI 3.0.1 specifications were not displaying in Exchange. The problem was caused by conditional rendering that removed the examples section from the DOM when shouldRenderExamples was false, and a complex mediaType calculation that could result in undefined. The fix ensures the examples section always exists in the DOM (using ?hidden attribute for visibility control) and directly uses this.mediaType without additional calculations, ensuring examples render correctly for OAS 3.0.1 specs with allOf inheritance and multiple examples.

v6.6.59

Bug Fixes

• OAS 3.0.0 array response examples: Fixed an issue where example payloads were not displaying on Exchange asset pages for OpenAPI Specification (OAS) 3.0.0 APIs with array response types. Examples were visible in Design Center's "Documentation" view but failed to render on Exchange, blocking partner automation workflows. This fix ensures that array response examples are properly displayed alongside their media type information, matching the behavior of object response types. RAML specifications were unaffected by this investigation. (W-21156905)

v6.6.58

• gRPC API detection: ApiConsoleApp now detects gRPC APIs and automatically hides the Try It panel (both inline and button) when a gRPC API is loaded. The detection runs when the AMF model changes to ensure correct visibility state. (W-21045326)

v6.6.57

What's Changed

W-21045342-PR: [APIC-Agent topic] Add Agent Topic icon on operations
W-21045326-PR: [APIC-gRPC] Hide Try it panel for gRPC specs

• Agent Topic icon rendering fix: Enhanced the AmfHelperMixin to properly resolve custom domain properties across different JSON-LD formats. This improvement ensures that the Agent Topic icon is correctly displayed on operations in the api-summary component, fixing an issue where the icon was missing when using the shorter AMF format. The fix includes better handling of custom domain properties resolution, supporting both expanded and compacted JSON-LD structures. (W-21045342)

• gRPC Try It panel visibility: Added automatic detection and hiding of the Try It panel for gRPC API specifications. When a gRPC API is detected using the _isGrpcApi() method from AmfHelperMixin, the console now:
  • Hides the inline try-panel that appears in wide layout mode
  • Hides the Try It button in the method documentation view
  • Provides a cleaner interface for gRPC APIs where the Try It functionality is not applicable

Full Changelog: v6.6.55...v6.6.57