---
schema_version: "1"
id: 1d150ce5932a00f4534952fd3299d7917236fd2684bf1b440fa039ed7e18b88d
title: Sync Your API Projects with MuleSoft VCS Using API Sync
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/studio/api-sync.md
canonical_url: https://docs.mulesoft.com/studio/api-sync
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1f0bf20be68db371b3a5305e6803d22bdc360c3c55b3d67d246427b9d6aa94ba
description: MuleSoft Documentation Site
latest: true
---
---
product: Studio
keywords: api, anypoint platform, sync, api sync, MuleSoft VCS
---

# Sync Your API Projects with MuleSoft VCS Using API Sync

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

API Sync in Anypoint Studio synchronizes your API specifications and Mule application projects with
MuleSoft VCS and Exchange. Use it to design, import, edit, and scaffold flows from RAML, OAS 2.0,
and OAS 3.0 API specs.

With API Sync, you can:

- Start designing a RAML, OAS 2.0, or OAS 3.0 API spec in Studio and sync it with API Sync.

- Pull a published RAML, OAS 2.0, or OAS 3.0 API spec from Exchange or from a private Maven
  repository, into your Mule application project in Studio to scaffold a new project.

- Edit the API spec you imported from Exchange, and push your changes to MuleSoft VCS.

- Scaffold multiple flows in different Mule configuration files by using API Sync on more than one
  API spec.

- Monitor the API versions that you implement in your project and update your flows based on the
  latest published version.

- Pull a RAML, OAS 2.0, or OAS 3.0 API spec from MuleSoft VCS into Studio, edit the spec offline,
  and push the updates back to MuleSoft VCS.

- Develop your Mule applications using API lifecycle development practices.

API Sync supports importing both RAML, OAS 2.0, and OAS 3.0 spec.

API Sync is bundled by default with Studio and requires Mule 4.1.4 or later.

API Sync doesn’t work properly if the RAML file exceeds 4,000 lines of text.

## Create an API Spec in Studio

Start a new API spec project in Studio. See
[Create an API Specification Project in Anypoint Studio](https://docs.mulesoft.com/studio/create-api-specification-studio) for more
information.

## Import an API Spec from Exchange

Import an API spec from Exchange into a new Mule project or from MuleSoft VCS into an editable API
spec project.

See [Import and Implement an API Specification from Exchange](https://docs.mulesoft.com/studio/import-api-specification-exchange) for
more information.

See [Update an Imported API Specification to the Latest Version](https://docs.mulesoft.com/studio/sync-update-api-spec) for more
information about keeping your Studio projects up to date with the latest version of an API spec.

See
[Edit API Specifications Offline and Sync Them with MuleSoft VCS](https://docs.mulesoft.com/studio/sync-api-projects-design-center)
for more information.

### Edit the Imported API Spec in Studio

Edit the imported API spec in your project as an API spec project.

1.  Import the API spec from Exchange to your Studio project.

2.  Sync it to MuleSoft VCS.

3.  Publish it to Exchange.

4.  Import the new version of your API spec.

See
[Edit an Imported API Specification and Publish the Changes](https://docs.mulesoft.com/studio/sync-imported-api-specifications-design-center)
for more information.

## See Also

- [Design, Publish, and Implement API Specifications in Anypoint Studio](https://docs.mulesoft.com/studio/api-development-studio)

- [Import and Implement an API Specification from Exchange](https://docs.mulesoft.com/studio/import-api-specification-exchange)

- [Import and Implement an API Specification from Maven](https://docs.mulesoft.com/studio/import-api-specification-maven)