pub.csp.file:addFile

Adds a new file into the CSP indicated by the friendlyName and creates a new contentID if one is not provided. One or both of contentID and nodeID fields can be provided, but at least one needs to be provided; that is why BOTH are listed as required. If both are provided then the nodeID takes precedence. If both are null, a service error results.

contentID	String The contentID of the object in the CSP with which the file is associated. Represents a globally unique ID, or GUID. If a contentID is not provided, one is created at the supplied nodeID.
nodeID	String The ID of the node
fileName	String The name of the file to be added
fileInputStream	String (Base64 encoded) Either a Base64 encoded byte stream of the file to be added, or the full path to the file
friendlyName	String Identifies the CSP server where the file is located
metadataMap	HashMap <String,String> or String Optional. Contains a collection of key-value pairs that represent data about the created node. This can be either a String in the form of comma-separated key=value pairs or a HashMap with key-value pairs entered at each map index/position. This allows you to associate any desired metadata key-value pairs with the created contentID.

contentID	String The supplied contentID, or the created contentID if one was not supplied
fileID	String The ID of the file
status	String Indicates success or failure

You can supply a contentID and a nodeID, or only one of these. Both fields are considered required. At least one must be supplied. If both are supplied, nodeID takes precedence. If both are null, an error results.