Upload a Linked File (Using Origami Storage)

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Overview

This endpoint uploads a linked file that becomes associated with a specific parent record (as defined by the {domain} and {id} values).

For example, if I want to upload a file for Policy 12345, then the route will be: /Files/Upload/Policy/12345

If you want to upload a file to Claim 76543 then the route will be:
/Files/Upload/Claim/76543

Content Type Requirements

Requests to this endpoint must use the multipart/form-data content type. The file itself is submitted as one part of the form-data payload.

Form-Data Attributes

For example purposes, this reference only shows the following fields:

  • FileName
  • Description

You are not limited to these fields. Any attribute defined in the Files domain may be supplied.
See the, Files Data Dictionary for a full description of all fields.

Path Params
string
required

This should match to the Domain Name in the system. It is case-sensitive. For Client Defined Entities it should start with 'Custom.'

integer
required

Numeric primary identifier for record to be updated.

Query Params
boolean
Defaults to false

This field lets you decide whether creating this domain record should trigger a corresponding system event. If you’ve got external workflows or Data Entry Events and you don’t want them firing, be sure to set the value to false.

Body Params
file
required

This is the encoded file.

string
required

This is the name of the file in the destination file system. Please include the file extension.
Please use standard best practices for choosing your filename (avoid spaces and long filenames, etc).

string

A human readable description of what the file is. In the Origami UI this could appear as a the clickable hyperlink anchor text. If null, then the FileName will be used as the description.

Response

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