Send a campaign through an active workspace channel. You can use the template already stored on the campaign or a template specified explicitly in the request.
POST https://api.platica.mx/v1/campaigns/{campaignId}/send
URL parameters
Parameter
Type
Description
Requirement
campaignId
string
Unique identifier of the campaign
required
Request examples
Immediate send using the template stored on the campaign
data contains the response from the upstream sending service, so its structure can vary across workspaces or integrations.
Notes
channelId is the SENDER channel. Legacy phone numbers and IDs remain accepted and are normalized to the canonical channel.
responderAgentId is independent from the channel. When omitted with a canonical channel, new conversations start initiated and unassigned. channel.defaultAgentId is not inherited. A legacy agent-phone identifier still preserves that inferred agent.
Reused active conversations keep their current agent.
Contacts with status: "blocked" are always excluded, even when sendToUndeliverable is true. If the entire audience is blocked, the API returns 409.
If template.name is omitted, the campaign's saved template is used. If the campaign has no configured template, the send fails with 400.
The number of items in params must match exactly the number of variables expected by the template.
If you send buttons, the number of buttons and their indexes must exist in the validated template.
When the template needs media, file must be a valid http or https URL.
All scheduledDates must be in the future at request time.