---
schema_version: "1"
id: 16e35fe35f4c49c4b06bb4789d973faf2c766ab362ba4f4c4b1e76211429a790
title: APIkit Mule4-1.2.0 Release Notes
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/apikit/apikit-4.1.20-release-notes.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.20-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: e8e53f2b0778415d0c396d0fb4b0c408f8f961b37597b53a16e240a17a24cb6b
description: MuleSoft Documentation Site
latest: true
---
# APIkit Mule4-1.2.0 Release Notes

**January 7, 2019**

This release notes briefly describe the new features released in APIkit 1.2.0.

## [](#whats-new)What’s New

- APIkit is now using AMF as the default framework to parse APIs and to validate all incoming requests.  
    AMF provides a way to achieve a unified behavior both at design time (Designer Center) and during runtime as well as OAS support. If needed, there is a way to use the previous RAML parser by specifying it in the apikit `config` tag.
- API Console was upgraded to version 5, which also uses AMF to read the API. This console is displayed when AMF is used.  
    When specifying RAML parser in the config, the old console is displayed.
- Query String validation support.

## [](#compatibility)Compatibility

- Mule Runtime 4.1.2 and later
- Anypoint Studio 7.2.0 and later
- Java Parser RAML 1.0 v1.0.29
- Java Parser RAML 0.8 v0.8.29
- API Console 4.2.1
- API Console 5

## [](#limitations)Limitations

- When using RAML parser to parse APIs and validate requests against them, the API Console used is the 4.2.1 version.
- Validations on query string over either scalar or arrays types are not performed.

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

- [Known Issues](https://help.salesforce.com/s/issues)