Automate campaigns
Account-token management of automation campaigns and their upload file-header (column-mapping) configurations, called by account users.
Account-token management of automation campaigns and their upload file-header (column-mapping) configurations, called by account users. List automation campaigns lists the caller's automation campaigns (with their file_header); Create file headers–Get sample file info create, read, update, delete a campaign's file-header config and fetch the associated S3 sample-file metadata. All scoped to the caller's person.company_id; file uploads go to S3..
Prerequisites
- A bearer token in the
Authorizationheader. Any endpoint that needs no token says so on its own page. - The id of each record the call targets. Every endpoint page lists the ids it needs.
Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Individual endpoints may return more; each page lists its own.
Endpoints
GET — Paginated list of the caller's automation campaigns (rs_campaigns.type = 'automation'), each including its file_header configuration (headers map, sample-file path, location identifier).
POST — Create the file-header (column-mapping) configuration for an automation campaign and upload the sample file to S3.
GET — Get the file-header configuration(s) for a given automation campaign.
DELETE — Delete a file-header configuration and its associated sample file from S3.
GET — Get the S3 URL and metadata (name, size, mime type) for the sample file attached to a file-header configuration.
Updated 11 days ago