Approve, reject or add campaign leads
Approve, reject or reset leads, by ids, all, or a rule; or add leads by id.
POST/api/v1/campaigns/{id}/leads
Parameters
Path
| Name | In | Description |
|---|---|---|
idrequired | path | The record's id. |
Body
A JSON object. Fields not listed are ignored.
| Name | In | Description |
|---|---|---|
action | body | approve, reject, include, exclude or reset. Omit to add leads. One of approve, reject, include, exclude, reset. |
lead_ids | body, array | Lead ids. |
all | body, boolean | Apply to every lead. |
rule | body, object | {min_icp_score, tiers, email_statuses}. |
added_from | body | manual, csv or research when adding. |
Example
curl
curl -X POST "https://crm.ashwanth.dev/api/v1/campaigns/{id}/leads" \
-H "Authorization: Bearer $SALES_ENGINE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"action": "approve",
"lead_ids": [],
"all": false,
"rule": {},
"added_from": ""
}'CLI
sales-engine campaigns approve-leads <id>The JSON above lists every documented field with a typed placeholder; send only the ones you mean.
Response
A 200 with the result under data, on creation too. Errors come back as an error object with a stable code; see Errors.
Shape
{
"data": { ... }
}Run it below to see the live shape for your workspace.
Try it
Runs against this server, as the workspace behind the key. Kept in this page while you browse the docs, gone on reload, never stored. Signed in to the app? Leave it blank and the call runs as you.
Path
requiredThe record's id.
Every documented field is listed above; leave out the ones you do not need.
Request
POST /api/v1/campaigns/%7Bid%7D/leads
Fill the path first.