Scheduled.Authorization: Bearer <token>. Get it with the sign-in call (POST /api/customer-users/partner-login).POST /api/v2/campaigns) and the same rules apply.scheduleDate the campaign is set to start at the next 5-minute mark of the clock (UTC).data[0] is the id of the campaign.isOptin, sendToAll, maxContactsCount and optinConsentAcknowledged are replaced like every other field: left out, they go back to their defaults. recipients is the exception: left out, the recipients written in the campaign are kept, and an empty list removes them.curl --location --request PUT 'https://api.veloconnect.me/api/v2/campaigns/9a4d6f20-1c3e-4b7a-8f52-6d0e1b2c3a4f' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"name": "October offer",
"scheduleDate": "2026-10-12T10:00:00",
"timezone": 4,
"timezoneId": "Asia/Yerevan",
"segmentIds": [
57
],
"quickAddPhoneNumbers": [],
"quickAddEmails": [],
"saveQuickAddAsContacts": false,
"channels": [
{
"providerType": "SMS",
"priorityOrder": 1,
"communicationType": "Promotional",
"message": "Hello {{name|customer}}, 20% off all orders until Sunday. MyBrand",
"senderId": 124,
"customerTrunkId": 18
}
]
}'{
"data": [
"9a4d6f20-1c3e-4b7a-8f52-6d0e1b2c3a4f"
]
}