Skip to main content
POST
Upload an automation action parameter attachment

Upload Format

This endpoint takes a multipart/form-data request (not JSON:API format) with the file in a file field. The file name and MIME type are taken from the uploaded file. When sending multipart, don’t set the Content-Type header yourself. Your HTTP client sets multipart/form-data with the boundary when you attach the file.

Example (cURL)

Deprecated: raw body upload

Sending the raw file as the request body is still accepted but deprecated and will be removed. Until you switch to multipart, keep sending both headers: Content-Type with the file’s MIME type and Content-Disposition: attachment; filename="<name>".

Authorizations

Authorization
string
header
required

OAuth 2.0 authentication. Use the client credentials or authorization code flow to obtain an access token.

X-Clarus-Subdomain
string
header
required

The subdomain/tenant name identifying which tenant's data to access. Required for all API requests.

Path Parameters

automation_action_parameter_id
integer
required

The unique identifier of the automation action parameter

Body

multipart/form-data
file
file
required

The file to upload

Response

Attachment uploaded successfully