Update file headers

Update an existing file-header configuration. Here the {id} path segment is the file-header id (campaign_automation_file_headers.id). The endpoint updates only the fields supplied; a new sample_file replaces and deletes the previous S3 object. Sent as multipart/form-data. Emits an audit event (CAMPAIGN_FILE_HEADERS_UPDATED).

Auth

  • Account bearer. The owning campaign must belong to the caller's person.company_id and be of type automation, else 403.

Rate limit

  • No rate limit.

Path params

FieldTypeRequiredNotes
fileHeaderIdintegerRequiredThe file-header id (route constrained to [0-9]+).

Body (multipart/form-data — all optional)

FieldTypeRequiredNotes
headersstring (JSON)Optional`nullable
sample_filefileOptionalmimes:xlsx,xls,csv, max 10 MB.
location_identifierstringOptionalMax 255.

Behaviour

  • 200 with the refreshed row under data.data.
  • 400 if headers is provided but malformed / missing keys / non-string values.
  • 403 if the caller does not own the config's campaign or is not an automation campaign.
  • 404 if no file-header row matches {id}.

Errors: 422 on validation failure.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Body Params
string
file
string
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json