> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Get started with the Web Forms API

> Learn about what you'll need to start making Web Forms API calls.

> **Note**
>
> The Web Forms API is available in all developer accounts, but only in certain production account plans. Contact [Docusign Support](https://support.docusign.com/s/?language=en_US) or your account manager to find out whether the Web Forms API is available for your production account plan.

To start making Web Forms API calls, you need:

* A free Docusign [developer account](/platform/account).
* An [app and integration key](https://admindemo.docusign.com/authenticate?goTo=appsAndKeys) in the developer environment. The integration key, sometimes referred to as a *client ID*, and the settings associated with it are required to [authenticate](/docs/web-forms-api/plan-integration/authentication) with the Docusign platform so that you can make API requests. See [Configure your app](/platform/configure-app) for details about how to set up an app and integration key. If you run Web Forms API examples from [Quickstart](/docs/esign-rest-api/quickstart), the tool automatically sets up an app and integration key in your developer account.
* A [web form configuration](/docs/web-forms-api/web-forms-101/concepts#web-form-configurations) in your developer account. A web form configuration defines the content and behavior of a web form and must be created and activated using the [Web Forms builder](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=gpc1660591510274.html). To access it, log in to the [eSignature web application](https://account-d.docusign.com/), select **Templates** from the top navigation, select the **Start** button in the left navigation, then select **Web Forms** > **Create Web Form**. If you run Web Forms API examples from [Quickstart](/docs/esign-rest-api/quickstart) or the [code example launchers](/docs/web-forms-api/how-to/code-launchers), you will receive instructions for creating and activating a web form configuration from a JSON file that these tools automatically generate.

## Developer tools

These tools provide sample code to help you start making Web Forms API calls:

* [Quickstart](/docs/esign-rest-api/quickstart) provides executable Web Forms API code examples in Bash, C#, Java, Node.js, PHP, PowerShell, Python, and Ruby that run under an app and integration key that Quickstart automatically creates in your developer account.
* [Code example launchers](/docs/web-forms-api/how-to/code-launchers) offer the same code examples as Quickstart, but they require manual configuration for authentication. Instructions are provided in each code launcher’s README file.
* The Web Forms API [Postman collection](/tools/postman) is a library of API requests that you can execute.
* [API Explorer](/tools/api-explorer) enables you to send test requests from the [API reference](/docs/web-forms-api/reference) method pages and review the responses without authenticating or configuring a project.
* The [Web Forms Sample App](https://webforms.sampleapps.docusign.com/) sample app provides a demo that you can run without installing or building a project. You can also download the source code, written in C# and React.js, to run it locally and use it to start building your own integrations.

## Next steps

* See [Plan a Web Forms API integration](/docs/web-forms-api/plan-integration) for an overview of the implementation details that you should consider before starting work on your application.
* See [Endpoint base path](/docs/web-forms-api/web-forms-101/endpoint-base-path) for information about constructing API endpoint URLs.
* See the [API reference](/docs/web-forms-api/reference) for a complete list of Web Forms API endpoints and their paths.