---
schema_version: "1"
id: 754865fc2c620b7a9b633581455001c1ba190dd14637abe8c96f10fa359d2de2
title: APIkit Mule4-1.2.0 Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/apikit/apikit-4.1.20-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/apikit/apikit-4.1.20-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 9e8afff238c0379db26980135e4fd9b84b39904e2472971d703c2b241d8769be
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# APIkit Mule4-1.2.0 Release Notes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

**January 7, 2019**

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

## 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

- 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

- 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

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