---
schema_version: "1"
id: 1d2cd083d26e48aa22cf923e74e983f474e73b8b7849c84c8dd02ba78a1d6527
title: Designing API Specs and Fragments
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/design-center/design-designing-api-specs-fragments.md
canonical_url: https://docs.mulesoft.com/design-center/design-designing-api-specs-fragments
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 468d66e4ecb3da22277fefaab39b2440cc2fda4946fca2c8f68eaa83320d0bd4
description: MuleSoft Documentation Site
latest: true
---
---
product: Design Center
---

# Designing API Specs and Fragments

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

Use API Designer to create, design, test, and publish new API Specifications.

## Design Using the Text or Visual Editor

You can use either [the text editor](https://docs.mulesoft.com/design-center/design-create-publish-api-raml-editor) or
[the Visual Editor](https://docs.mulesoft.com/design-center/design-create-publish-api-visual-editor) to create API specifications.

With the text editor, you can:

- Design according to best practices with a context-aware shelf that auto-populates with the
  appropriate methods, resources, parameters, and security components.

- Include RAML API fragments, such as security schemas and data types, from Exchange or write your
  own.

- Apply rulesets from Exchange to validate the governance conformance of your projects.

- Import existing API specifications.

With the visual editor, you can:

- Create a specification for use cases in which you do not need to include RAML fragments.

- Scaffold a specification that you can complete and customize in the text editor.