> 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/entity-management-faqs/can-i-delete-test-or-submitted-applications.md). # Can I delete test or submitted applications? Drafts can be deleted. Applications cannot be deleted once they are submitted. To delete a Draft that was never submitted, use the discard command: ``` DELETE /merchant-onboarding/applications/drafts/{applicationId} ``` A successful discard returns `204 No Content` and permanently deletes the Draft and its attachments. It works only on applications in Draft status. See [Draft and Submit (Recommended)](/onboarding/draft-and-submit.md). As part of our compliance and record-keeping requirements, all applications must be retained on file once they are submitted, including those submitted with test data during development or sandbox testing. **Why can't submitted applications be deleted?** Submitted applications represent compliance-related records. Even in sandbox environments, we are required to preserve submission history rather than remove it entirely. **How should I manage test applications during development?** While submitted applications cannot be deleted, there are a few ways to make them easier to manage: * Discard Drafts you no longer need before submitting them * Sort applications by date to quickly isolate recent test submissions * Use available date filters (for example: last hour, last day, last week) to narrow results * Adopt a naming or reference convention during testing to clearly distinguish test data from real submissions * Use [Cancel Application](/onboarding/cancel-application.md) to move applications you no longer need out of an active status before they're submitted **Can I at least get a test application out of the way?** Yes, if it hasn't been submitted yet. Discard removes a Draft entirely. [Cancel Application](/onboarding/cancel-application.md) moves an application to `withdrawn` while it's still in `draft`, `viewed`, or `signing` status. The record isn't deleted, but `withdrawn` is a terminal status, so a cancelled test application won't show up as something still in progress. This only applies before submission. Once an application reaches `submitted` status or later, neither Discard nor Cancel Application is available, and the record stays as-is per the record-keeping requirement above. There is currently no way to mark a submitted application as inactive. --- # 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/entity-management-faqs/can-i-delete-test-or-submitted-applications.md?ask=&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.