Post
/data/actionStatuses/{actionId}/attachments
Upload an attachment to a specific action, for instance the picture of a replaced component or the service report signed by the technician.
The file is sent as multipart form data, and the historical parameter selects whether the attachment belongs to an upcoming or a historical action.
Security
HTTP
Type bearer
Header parameters
X-Servitly-Tenant
stringRequired
The name of the tenant (e.g. acme).
Path parameters
actionId
stringRequired
The id of the action to add the attachment to.
Minimum1.0
Exampleabcd1234
Query parameters
historical
booleanRequired
If true, the action is created as historical, else as upcoming.
Body parameters
The attachment file.
object
file
string Required
Responses
200
Attachment created.
400
Request data not valid.
object
message
string
The error response.
ExampleBad request
401
User not authenticated.
object
message
string
The error response.
ExampleUser not authenticated
403
User not authorized.
object
message
string
The error response.
ExampleUser not authorized
429
API call rate limit exceeded.
object
message
string
The error response.
ExampleAPI call rate limit exceeded
500
Internal server error.
object
message
string
The error response.
ExampleInternal Server Error