> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/faqs-and-troubleshooting/onboarding-faqs/how-do-i-create-an-application-in-draft-status.md).

# How do I create an application in Draft status?

The recommended way to create a Draft application is the dedicated Draft endpoint:

```
POST /merchant-onboarding/applications/drafts
```

A Draft is never sent to the signer until you submit it. Only `partnerId` and `merchantName` are required, so you can save whatever merchant data you have and add the rest later.

Example:

```json
{
  "merchantData": {
    "partnerId": "partner_123",
    "merchantName": "Northwind Coffee Roasters",
    "registeredName": "Northwind Coffee Roasters LLC",
    "stakeholders": [
      {
        "firstName": "Morgan",
        "lastName": "Reed",
        "email": "morgan.reed@example.com",
        "phoneNumber": "+15085550101",
        "jobTitle": "Owner",
        "isApplicationSigner": true
      }
    ]
  }
}
```

The response includes the `applicationId`. Use it to update the Draft, upload supporting documents, discard the Draft, or submit it.

When the Draft is ready, submit it:

```
POST /merchant-onboarding/applications/{applicationId}/submit
```

After this command is called, the application moves forward into the signing flow. Attachments can only be added while the application is still in Draft status.

**Alternative: create a Draft with the original create endpoints**

If your integration already uses `POST /merchant-onboarding/applications` or `POST /merchant-onboarding/applications-short`, you can create a Draft by setting `submitImmediately` to `false`:

```
{  "submitImmediately": false}
```

By default, those endpoints create and submit the application immediately so the signer can begin the signing flow. This preserves the standard behavior for existing integrations. When `submitImmediately` is `false`, Bead creates the application but does not move it into the signing flow, and you submit it later with the same submit command shown above.

Related documentation:

* [Draft and Submit (Recommended)](/onboarding/draft-and-submit.md)
* [Submit Application, Submit behavior](https://developers.bead.xyz/onboarding/submit-application#submit-behavior)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bead.xyz/faqs-and-troubleshooting/onboarding-faqs/how-do-i-create-an-application-in-draft-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.