Legacy compatibility
APIkit Compatibility
Compare APIkit module support on Mule 3 and Mule 4 before you choose an implementation stack. Review protocol and language coverage in the tables on this page when you plan AsyncAPI, gRPC, GraphQL, OData, REST, or SOAP APIs. For APIkit versions that align with FIPS 140-2 expectations, see APIkit Release Notes.
| Module | Mule 3 | Mule 4 |
|---|---|---|
APIkit for AsyncAPI |
No |
Yes |
APIkit for gRPC |
No |
Yes |
APIkit for GraphQL |
No |
Yes |
APIkit for OData v2 |
Yes |
Yes |
APIkit for OData v4 |
No |
Yes |
APIkit for REST |
Yes |
Yes |
APIkit for SOAP |
Yes |
Yes |
APIkit for SOAP Module Versions and Mule Runtime
APIkit for SOAP 1.7.0 provides broad Mule runtime compatibility. APIkit for SOAP 2.0.0 is the major successor to 1.6.10 and requires JDK 17 and Mule runtime 4.9.11 or later. APIkit for SOAP 1.6.5 through 1.6.10 are deprecated.
APIkit for SOAP Versions
| Line | Version | Minimum Platform | Use Cases |
|---|---|---|---|
1.7.0 |
JDK 8, 11, or 17; Mule runtime 4.1.x and later |
You must keep existing deployments on earlier Mule or Java stacks without adopting the 2.x requirements. |
|
Modern major |
2.0.0 (successor to 1.6.10) |
JDK 17 only; Mule runtime 4.9.11 and later |
You standardize on current Mule and Java 17. You choose the version that receives new features. |
Deprecated |
1.6.5 – 1.6.10 |
Don’t adopt or standardize on these releases. |
Migrate to 1.7.0 or 2.0.0 using the version selection guide. |
See Choose the APIkit for SOAP module version and Before You Begin Using APIkit for SOAP when you plan upgrades.
Language and Protocol Support
| Language/protocol | Version |
|---|---|
AsyncAPI spec |
2.6 |
Protocol Buffers (gRPC) |
3 |
OData |
2.0 and 4.0 |
OpenAPI Specification (OAS) |
2.0 and 3.0 |
RESTful API Modeling Language (RAML) |
1.0 and 0.8 |
SOAP |
1.1 and 1.2 |



