> 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

# Endpoint base path

> Learn how to construct the endpoint base path for 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.

The base path for Web Forms API endpoints is:

`{base_uri} + "/api/webforms/v1.1/accounts/" + {api_account_id}`

This table has information about base URIs. It also lists the login URLs for the eSignature web application, which includes a Forms module that enables you to create and manage [web form configurations](/docs/web-forms-api/web-forms-101/concepts#web-form-configurations).

| Environment | API base URI                  | Web application login URL        |
| ----------- | ----------------------------- | -------------------------------- |
| Developer   | `https://apps-d.docusign.com` | `https://account-d.docusign.com` |
| Production  | `https://apps.docusign.com`   | `https://account.docusign.com`   |

You can find your API account ID on the [Apps and Keys](https://admindemo.docusign.com/authenticate?goTo=appsAndKeys) page.

To construct a complete endpoint URL, append the endpoint path to the base path. Endpoint paths appear in the [API reference](/docs/web-forms-api/reference). For example, the endpoint URL for an [Instances:createInstance](/docs/web-forms-api/reference/webforms/instances/createinstance) request on the developer environment would look like this:

`https://apps-d.docusign.com/api/webforms/v1.1/accounts/{api_account_id}/forms/{form_id}/instances`

> **Note**
>
> Before your application can make requests to the production environment, it must complete a [Go-Live](/docs/web-forms-api/go-live) process.

## Production data center auto-routing

Docusign has multiple production data centers. Some Docusign APIs require an [/oauth/userinfo](/platform/auth/reference/user-info) call after [authentication](/docs/web-forms-api/plan-integration/authentication) to determine the data center host name for the production base URI. The Web Forms API automatically routes API requests to the correct data center for your production account, so your application does not need to make a `userinfo` call.

## Next steps

* See the [API reference](/docs/web-forms-api/reference) for a complete list of Web Forms API endpoints and their paths.
* See [Go-Live](/docs/web-forms-api/go-live) for information about the process to move your application from the developer environment to production.