> 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?

By default, Bead creates and submits onboarding applications immediately so the signer can begin the signing flow. This preserves the standard behavior for existing integrations.

If you need to upload supporting documents before the application is sent for signing, create the application in Draft status by setting:

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

Use this flag when calling the application creation endpoint:

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

or, if using the minimal application flow:

```
POST /merchant-onboarding/applications-short
```

When `submitImmediately` is set to `false`, Bead creates the application but does not immediately move it into the signing flow. The returned `applicationId` can then be used to upload supporting documents while the application remains in Draft status.

Example:

```
{  "submitImmediately": false,  "signerInfo": {    "name": "Morgan Reed",    "email": "morgan@example.com",    "position": "Owner"  },  "merchantData": {    "registeredName": "Northwind Coffee Roasters LLC"  }}
```

After the application is created in Draft status, upload any required attachments to the application.

When all attachments are complete, submit the Draft application using:

```
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.

Related documentation:

[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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.