> For the complete documentation index, see [llms.txt](https://postman-v2.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postman-v2.guides.gov.sg/general-users-ui-portal/campaign-settings/delete-your-campaign.md).

# Delete your campaign

### 1. Campaign deletion features

#### You will no longer be able to do the following once a campaign is deleted

1. You cannot retrieve a deleted campaign: 

   1. Campaign deletion is an **irreversible process**

2. No access to campaign
   1. No message can be sent out via this campaign, whether through the admin portal,  API or SFTP 
   2. No access to campaign logs - you will not be able to retrieve logs for this campaign
   3. No access to campaign or settings by all users except the agency's PIC

      1. This includes all members of the campaign that you have deleted

3. Unable to call the API endpoints with this campaign ID
   1. No access to campaign's settings, including API keys and whitelisted IP addresses
   2. Please ensure no one from your agency/vendors are using this campaign before deleting it

#### Actions that are still available after a campaign is deleted

1. Agencies will still be charged for messages sent from this campaign before campaign deletion
   1. Follows Postman billing

      1. Refer to our billing page in our policy guide for more information

2. Agency Person(s) In-charge (PICs) will still be able to view deleted campaigns by users in their agency 
   1. Able to do so via the Admin Dashboard

#### 2. When should you delete campaigns <a href="#id-2.-when-should-you-delete-campaigns" id="id-2.-when-should-you-delete-campaigns"></a>

**Scenario 1: Campaign created for testing purposes**

You have created a campaign to test out how to create a campaign, send a message and how to access the campaign settings.

* No messages to MOPs were sent out through this campaign

You **may delete** this campaign as it is a campaign that you've created to try Postman out - the campaign was created for testing purposes.

* For API users: Before deleting this campaign, you should make sure that **no other user/vendor** is using this campaign when calling Postman’s API endpoints.
* If messages were sent out
  * Before 1 July 2025: messages paid for by MDDI
  * From 1 July 2025: messages paid for by your agency

**Scenario 2: Campaign that is no longer in use**

It is now December. You have created this campaign for an event in August. Messages were sent out via Postman to MOPs in the month of August and you are not using the campaign now.

* You are not planning to use this campaign now (December)

You **should not delete** this campaign as:

* You will no longer be able to retrieve campaign logs once you have deleted this campaign
  * you may need the logs when your agency is doing reconciliation of messages sent out by your agency
* This campaign is not being used now, but may be used again in the future.


---

# 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, and the optional `goal` query parameter:

```
GET https://postman-v2.guides.gov.sg/general-users-ui-portal/campaign-settings/delete-your-campaign.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.