--- schema_version: "1" id: 8f63d61ecd9ae4f42addc5b395c602586db8e5a21fa6de6faf8c49ad8de3737c title: Import and Implement an API Specification from Maven collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/studio/import-api-specification-maven.md canonical_url: https://docs.mulesoft.com/studio/import-api-specification-maven source_site: docs.mulesoft.com content_type: documentation content_hash: c3b06b1d6ebdcd6a8213acbf6bf93a40f7aa039805338fca2d0fc40bb2c83f1d description: MuleSoft Documentation Site latest: true --- --- product: Studio --- # Import and Implement an API Specification from Maven > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Studio enables you to import a RAML or OAS 2.0 and 3.0 API specification into either a new Mule project or an existing one. If you’re using Mule runtime engine (Mule) 4.1.3 and earlier, or if you prefer to import an API specification that’s not in Exchange, follow the steps presented in [import an API specification from a local file](https://docs.mulesoft.com/studio/import-api-specification-local-file) or [import an API specification from MuleSoft VCS](https://docs.mulesoft.com/studio/import-api-specification-design-center) depending on your preferred use case. ## Import and Implement an API Specification From Maven into a New Project 1. In the taskbar of the Anypoint Studio display, select **File** > **New** > **Mule Project**. 2. Type a name for your project. 3. Select a Mule runtime engine version 4.1.4 or later. 4. In the **API Specification** section, select the **From Exchange or Maven** tab, click the **Add** icon (![2%](/mulesoft/current/en-us/studio/_images/add-icon.png)) and select **From Maven**. You can either specify the Maven coordinates of your API specification, or you can install a local file into your Maven repository. ### Add an API Specification From Maven Coordinates If your API specification is in your corporate Maven repository, you can add it as a dependency. 1. In the **Import From Maven** screen, configure your API specification artifact definition: - Group ID - Artifact ID - Version 2. In the **Advanced Settings** section, verify that the **Classifier** value for your dependency is the same as your API specification type (RAML, for example). 3. Click **OK**. Studio scaffolds your API specification. If you choose not to create flows out of your API specification, unselect the **Scaffold Flows From These API Specifications** checkbox. After you import them, you can manage the API specifications in your project that are linked to Exchange from the API specification project management view by clicking the _Manage Mule Project APIs_ icon (![2%](/mulesoft/current/en-us/studio/_images/manage-project-api-icon.png)) in the taskbar. ### Add an API Specification From a Local File If you can’t download the API specification dependency from your corporate Maven repository, or if your API specification isn’t available in Maven, make your specification available as a dependency by installing it to your local Maven installation: 1. In the **Import From Maven** screen, next to the **Install a local dependency** field, click **Install**. 2. In the **File** field, either type the location of your file or click **Browse** to find it in your files. If you select **Browse**, change the file type to **any**. You can add either a RAML or OAS 2.0 and 3.0 specification, or a ZIP bundle file as your API specification, and click **Open**. 3. Set up the rest of your Maven coordinates for your API specification. 4. In the **Advanced Settings** section, verify that the **Classifier** value for your dependency is the same as your API specification type (RAML, for example). 5. Click **Install** and **OK**. Studio scaffolds your API specification. If you choose not to create flows out of your API specification, unselect the **Scaffold Flows From These API Specifications** checkbox. You can manage the API specifications in your project that are linked to Exchange from the API specification project management view by clicking the **Manage Mule Project APIs** icon (![2%](/mulesoft/current/en-us/studio/_images/manage-project-api-icon.png)) in the taskbar. ## Import and Implement an API Specification from Maven Into an Existing Project 1. In the Package Explorer view, select your project. 2. Click the **Add** icon (![2%](/mulesoft/current/en-us/studio/_images/add-icon.png)) and select **From Maven**. 3. You can either specify the Maven coordinates of your API specification, or you can install a local file into your Maven repository. ### Add an API Specification From Maven Coordinates If your API specification is in your corporate Maven repository, you can add it as a dependency. 1. In the **Import From Maven** screen, configure your API specification artifact definition: - Group ID - Artifact ID - Version 2. In the **Advanced Settings** section, verify that the **Classifier** value for your dependency is the same as your API specification type (RAML, for example). 3. Click **OK**. Studio scaffolds your API specification. If you choose not to create flows out of your API specification, unselect the **Scaffold Flows From These API Specifications** checkbox. After you import them, you can manage the API specifications in your project that are linked to Exchange from the API specification project management view by clicking the _Manage Mule Project APIs_ icon (![2%](/mulesoft/current/en-us/studio/_images/manage-project-api-icon.png)) in the taskbar. ### Add an API Specification From a Local File If you can’t download the API specification dependency from your corporate Maven repository, or if your API specification isn’t available in Maven, make your specification available as a dependency by installing it to your local Maven installation: 1. In the **Import From Maven** screen, next to the **Install a local dependency** field, click **Install**. 2. In the **File** field, either type the location of your file or click **Browse** to find it in your files. If you select **Browse**, change the file type to **any**. You can add either a RAML or OAS 2.0 and 3.0 specification, or a ZIP bundle file as your API specification, and click **Open**. 3. Set up the rest of your Maven coordinates for your API specification. 4. In the **Advanced Settings** section, verify that the **Classifier** value for your dependency is the same as your API specification type (RAML, for example). 5. Click **Install** and **OK**. Studio scaffolds your API specification. If you choose not to create flows out of your API specification, unselect the **Scaffold Flows From These API Specifications** checkbox. You can manage the API specifications in your project that are linked to Exchange from the API specification project management view by clicking the **Manage Mule Project APIs** icon (![2%](/mulesoft/current/en-us/studio/_images/manage-project-api-icon.png)) in the taskbar. ## See Also - [Design, Publish, and Implement API Specifications in Anypoint Studio](https://docs.mulesoft.com/studio/api-development-studio) - [Sync Your API Projects with MuleSoft VCS Using API Sync](https://docs.mulesoft.com/studio/api-sync) - [Maven Preferences Reference](https://docs.mulesoft.com/studio/maven-preferences-reference)