---
schema_version: "1"
id: 1df33508ce67e3fe252929ef2cf93063c5e78a29a1075d34c9b7be2fabce2a84
title: APIkit for AsyncAPI 1.1.0 Release Notes
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/apikit/apikit-for-asyncapi-1.1.0.rn.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-asyncapi-1.1.0.rn
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ad11166847a6532b7021f27815642aa3353073f275cb44c80e4ab77eb0450dba
description: MuleSoft Documentation Site
latest: true
---
# APIkit for AsyncAPI 1.1.0 Release Notes

APIkit for AsyncAPI supports scaffolding Mule apps with the AsyncAPI 2.6 spec in Anypoint Code Builder and Anypoint Studio. With this support, you can use asynchronous messaging protocols and design event-driven APIs.

## [](#october-8-2024)October 8, 2024

## What’s New

- APIkit for AsyncAPI now supports Avro schemas
    
    Improve data serialization for your API interactions. See [APIkit for AsyncAPI モジュールでの Avro スキーマの実装と検証](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-avro-support)
- APIkit for AsyncAPI now supports Solace PubSub+ Connector and Anypoint Connector for Salesforce Pub/Sub (Salesforce Pub/Sub Connector).
    
    Expand your integration capabilities and streamline event-driven architectures. See [Supported Message Brokers](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-module-reference#supported-message-brokers)
- Validation features are improved to create more robust and reliable API implementation.
    
    See [Validation of Messages](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-module-reference#validation-of-messages).
- Multiple message handling in an operation is now improved.
    
    Enhance the flexibility and scalability of your API operations

## Compatibility

<table class="tableblock frame-all grid-all fit-content spread">
<colgroup>
<col>
<col>
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Product</th>
<th class="tableblock halign-left valign-top">Version</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Anypoint Code Builder</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">October 8, 2024 and later</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Anypoint Studio</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">7.19.0 and later</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Mule runtime</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">4.6.0 and later</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">OpenJDK</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">8, 11, and 17</p></td>
</tr>
</tbody>
</table>

## Known Issues

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 50%;">
<col style="width: 50%;">
</colgroup>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Known Issue</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">ID</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">If you enable the validation and the <code>mediaType</code> of the message doesn’t match the <code>mediaType</code> specified in the API spec, the message isn’t flagged as invalid.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">W-16663560</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">AsyncAPI Message Listener doesn’t preserve the <code>mediaType</code> property and transforms it as the <code>defaultContentType</code> present in the Async API spec unless AsyncAPI Message Listener supports the inbound message type.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">W-16663585</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">In Salesforce Pub/Sub Connector, the source validation doesn’t work if <code>contentType</code> is application/XML.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">W-16756836</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">When implementing AsyncAPI APIs in Windows, an empty extra Mule-config file is created.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">W-15757808</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">APIkit for AsyncAPI connector fails while parsing Async APIs that reference Avro schema files.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">W-16896197</p></td>
</tr>
</tbody>
</table>

## [](#see-also)See Also

- [Salesforce Help](https://help.salesforce.com)
- [MuleSoft Services](https://www.mulesoft.com/support-and-services)
- [APIkit for AsyncAPI](https://docs.mulesoft.com/jp/apikit/latest/apikit-for-asyncapi)
- [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api)