---
schema_version: "1"
id: 0aa3c08f551a886e405c3d82d381c99336a489c4271d294358994905a9e877d4
title: Import Files into an API-Specification Project
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/design-center/design-import-files.md
canonical_url: https://docs.mulesoft.com/design-center/design-import-files
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 4a4704fcfa68e8615382f26f74395b328eb2cbb5f4d84255e94c65826916db92
description: MuleSoft Documentation Site
latest: true
---
---
product: Design Center
---

# Import Files into an API-Specification Project

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

> [!WARNING] File uploads are restricted to supported formats.

You can import RAML fragments, OAS components, and JSON schemas into an API-specification project.

You can include more than one API specification in an API-specification project. You might want to
have more than one specification in a project if the specifications are closely related in
functionality. You must set one of the specifications as the root file of the project. However, you
can change which file is the root file whenever you need to.

The fragments that you import can be written in RAML 0.8, RAML 1.0, or OAS 3.0. You can import
annotation types, data types, examples of JSON response payloads, libraries, resource types,
security schemes, and traits.

There are three locations that you can import from: your computer, a location at a URL, and Anypoint
Exchange.

## Procedure

- Import a file or the content of a `.zip` file that is stored on your computer, if you are using
  the text editor:

  1.  Click the gear icon in the top-right corner of the text editor and select **Import**.

  2.  In the **Import** dialog, select **File or Zip**.

  3.  Browse to your file or ZIP file and select it.

  **Result:** The file or files are listed in the left pane of the editor. If you imported a ZIP
  file that contains files that are in a folder structure, the folder structure is represented in
  the pane.

- Import a file that is available through a URL, if you are using the text editor:

  1.  Click the gear icon in the top-right corner of the text editor and select **Import**.

  2.  In the **Import** dialog, select **URL**.

      > [!NOTE]
      >
      > - If you import a file that is available online by providing its URL, be sure that the file
      >   contains no `!include` statements (RAML) or `$ref` statements (OAS). The editor imports
      >   only the file that is at the URL.

  **Result:** The file is listed in the left pane of the editor.

- To import an API specification or API fragment from Exchange, together with its dependencies:

  1.  Open the **Import Asset from Exchange** dialog by using either of these methods:

      - If you are using the text editor and your project contains only the default file that API
        Designer created together with the project, you can click the linked text that appears in
        the **Files** pane.

      - If you are using the text editor, you can click the gear icon in the top-right corner of the
        text editor and select **Import from Exchange**.

      - If you are using the visual editor and your project does not yet contain any resources or
        data types, you can click the linked text that appears in the **New API** pane.

  2.  In the drop-down menu in the top-left corner of the dialog, select the business group that
      owns the asset.

  3.  Select one of the assets, which are listed in a table that has these columns:

      **Name**

      The name of an API specification or API fragment.

      **Version**

      The version of a specification or fragment.

      Select the **Include snapshots** checkbox in the bottom-left corner of the dialog to include
      snapshots in this column.

      **Type**

      The type of asset.

      The value can be either **REST API** or **API Fragment**.

      **Language** (for API specifications being imported into the text editor)

      The language is either RAML or OAS.

      The value displayed by default is the language in which the specification was written. The
      non-default value is the language in which Exchange created a copy when the specification was
      published.

      If you want to import the copy, you might need to correct errors in it after you import it.
      The process that Exchange uses to create copies, which converts RAML to OAS or vice versa, is
      not guaranteed to produce error-free specifications.

      **Language** (for API specifications being imported into the visual editor)

      The language is always RAML.

      API Designer imports the RAML version of a specification, displays the RAML version in the
      **RAML** pane, and displays the OAS version in the **OAS** pane.

      **Language** (for fragments)

      You can choose between RAML, OAS, or JSON Schema.

      **Date modified**

      The date that the currently selected version of the currently selected asset was published.

      **Created by**

      The user ID of the person who published the currently selected version of the currently
      selected asset.

  4.  Click **Import Asset**.

  **Result:** The file or files are listed in the left pane of the editor.

## See Also

- [Root Files in Projects in the Text Editor](https://docs.mulesoft.com/design-center/design-change-root-file)

- [Design, Create, and Publish API Specifications](https://docs.mulesoft.com/design-center/design-create-publish-api-specs)