Troubleshooting the Boomi Files.com Partner Connector

The Files.com Partner Connector shape can fail for the reasons below. In each case, check the response document of the Files.com shape in your Boomi process to identify the cause.

Invalid API Key

Invalid or revoked API Keys return a response document containing the following error message:

{
  "error": "The API key or Session token provided could not be used to validate this request. Internal Error Code: API1",
  "http-code": 401,
  "instance": "0434fde9-1967-4019-a4db-02ddc2001a1e",
  "title": "Invalid Credentials",
  "type": "not-authenticated/invalid-credentials"
}

Update the connector with a valid API Key and retry the process.

Incorrect API Key Permissions

When your API Key does not have permission to access an item on Files.com, the response document contains the following error:

{
  "error": "Not Found",
  "http-code": 404,
  "instance": "fa8f115b-0ffd-4abd-a37e-dc91a4518c06",
  "title": "Not Found",
  "type": "not-found"
}

Confirm that the API Key has permission to access the item on Files.com, or switch to an API Key that does.

Trying to Use List Folder Items on a Non-existent Folder

Listing the contents of a non-existent folder produces the following error in the response document:

{
  "error": "Not Found",
  "http-code": 404,
  "instance": "fa8f115b-0ffd-4abd-a37e-dc91a4518c06",
  "title": "Not Found",
  "type": "not-found"
}

Confirm that the folder exists on Files.com. To explore the available folder structure, start your List Folder Items operation at /, the root folder.

Trying to Use Download A File on a Non-existent File

Attempting to download a non-existent file produces the following error in the response document:

{
  "error": "Not Found",
  "http-code": 404,
  "instance": "fa8f115b-0ffd-4abd-a37e-dc91a4518c06",
  "title": "Not Found",
  "type": "not-found"
}

Before attempting the download, confirm that the file exists by running the List Folder Item action against the folder containing the file.

Trying to Upload a File Into a Non-existent Folder

When the target folder does not exist, the Connector creates the entire folder path so that the file uploads successfully.

Trying to Upload a File Into a Folder Which Your API Key Has No Access Permissions For

When the API Key cannot access the target folder, the upload fails and the response document contains the following error:

{
  "error": "Not Found",
  "http-code": 404,
  "instance": "fa8f115b-0ffd-4abd-a37e-dc91a4518c06",
  "title": "Not Found",
  "type": "not-found"
}

Before attempting the upload, confirm that the API Key can access the target folder. Site-wide API Keys have access to all folders and do not produce this error. If the API Key is owned by a user account, confirm that the user account has access permissions to the target folder.