Reference
Edit a campaign
Rename / describe a campaign, set sender accounts (max 20, draft only) or audience.
View MarkdownThis page is generated from the source code on every release.
Rename / describe a campaign, set sender accounts (max 20, draft only) or audience.
Overview
| Name | Value |
|---|---|
| Code | campaigns.update |
| Scope needed | campaigns.write |
| Risk | Write |
| May need confirmation | No |
| Runs as | Answers right away |
Needs Idempotency-Key |
No |
| Member roles allowed | owner, manager |
| In the app | Campaigns → Settings |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
id |
uuid |
Yes | |
name |
text |
No | |
description |
text |
No | |
topic |
text |
No | |
goal |
"outreach" | "nurture" |
No | |
accountIds |
uuid[] |
No | |
audience |
object |
No |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/campaigns.update \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"id":"00000000-0000-0000-0000-000000000000"}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
Example answer
{
"data": {
"ok": true
}
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "campaigns.update". Tool name when listed: campaigns_update.