> For the complete documentation index, see [llms.txt](https://help.murlist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.murlist.com/api-documentations/campaign-api/add-prospect-to-campaign.md).

# Add prospect to campaign

Endpoint:

```
https://api.murlist.com/campaign/prospects/add
```

Required data:

In the request body, include data as follows:

```
{
    "campaign": "txxxxxxsiidoS8w8YER7xxxxxZBFV", //the campaign Id
    "prospect_email": "ik82i@yahoo.com", 
    "other_fields": {"name": " Ikenna Paschal", "anyKey": "anyValue"},
    "verify_email": true //false
}
```

#### Understanding the required data:

`campaign:` This should be the id of the campaign you want to add the prospect to. This can be gotten by calling the [list campaign API](/api-documentations/campaign-api/list-all-campaigns.md) which returns campaigns and their ids

`prospect_email`: This should be the email of the prospect you wish to add to an existing campaign.

`other_fields`: This should be an object(dictionary) of other attributes of this prospect like age, name, location. A combination of key/value pairs.\
These attributes are used in personalization.

`verify_email`: This verifies the prospect's email before adding them to a campaign if set to true and will skip verification if set to false. \
important to mention that the decision to send to prospect based on the verification status is made at the campaign level, during the campaign creation configuration.

#### What this API returns:

On successful addition, the API should return a status code 201, with the message, "Added successfully".\ <br>

If you need any help in implementing this API, be sure to reach out to us at <support@murlist.com>. We are always happy to help.


---

# 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://help.murlist.com/api-documentations/campaign-api/add-prospect-to-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.