---
schema_version: "1"
id: 8d8d603658d505615d002dc9d0a8490826ce04edd99da170bf02f367f3404028
title: Documenting an API
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/exchange/about-documenting-an-api.md
canonical_url: https://docs.mulesoft.com/exchange/about-documenting-an-api
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ea705d0800e1cf42de78771afd819f6085bf8d6e9f775ced94cc1116d3f52aa6
description: MuleSoft Documentation Site
latest: true
---
---
product: Exchange
---

# Documenting an API

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

To increase usability and adoption, create documentation using Einstein generative AI, document APIs
using API Notebook, and configure API instances.

- [Generating API Documentation with Generative AI](https://docs.mulesoft.com/exchange/generating-documentation-with-ai)

  Create API documentation by using Einstein generative AI.

- [Documenting an Asset Using API Notebook](https://docs.mulesoft.com/exchange/to-use-api-notebook)

  > [!NOTE] This feature of the product has reached
  > [End of Life](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf).

  Create API Notebooks to document each function in your API and provide a test area so that users
  can experiment with sending different values to the API and receiving output.

  After creating your API Notebook, create an API instance to control whether the notebook is
  private or public.

## See Also

- [Editing an Asset](https://docs.mulesoft.com/exchange/to-describe-an-asset)