Overview
Create and manage outbound calling campaigns
A campaign runs a workflow against a list of contacts. You upload a CSV of phone numbers, configure retry logic and scheduling, then start the campaign. Paladin dials contacts automatically up to your configured concurrency limit.
| Method | Endpoint | Quick Link |
|---|---|---|
POST | /s3/presigned-upload-url | Upload contacts CSV |
POST | /campaign/create | Create a campaign |
GET | /campaign/ | List campaigns |
GET | /campaign/{campaign_id} | Get a campaign |
PATCH | /campaign/{campaign_id} | Update a campaign |
POST | /campaign/{campaign_id}/start | Start |
POST | /campaign/{campaign_id}/pause | Pause |
POST | /campaign/{campaign_id}/resume | Resume |
GET | /campaign/{campaign_id}/progress | Get campaign progress |
GET | /campaign/{campaign_id}/runs | Get campaign call runs |
Campaign status values#
| Status | Description |
|---|---|
draft | Created but not started |
running | Actively dialing contacts |
paused | Temporarily stopped; can be resumed |
completed | All contacts processed |
failed | Campaign encountered a fatal error |
How to use this reference#
Use this page as the entry point for the related API endpoints. Open the endpoint-specific page when you need the exact method, path, request body, response schema, and OpenAPI details.
Implementation checklist#
- Start with the overview table to choose the correct endpoint.
- Confirm authentication and organization scope before calling the endpoint from code.
- Test with a small request first, then inspect the response and error handling path.