Troubleshooting the Boomi Files.com Partner Connector

The Files.com Partner Connector shape can fail for the reasons below. When an operation fails, the Files.com shape reports the error and your Boomi process stops.

The connector's List action does not report these errors; it completes and returns an empty result when the folder does not exist or the API Key is invalid.

Invalid API Key

Invalid or revoked API Keys produce the following error:

[401] The API key or Session token provided could not be used to validate this request.

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

Not Found

When the file or folder path does not exist on Files.com, or the API Key does not have permission to access it, the operation produces the following error:

[404] Not Found.  This may be related to your permissions.

Files.com returns this error for both causes.

Confirm that the path exists on Files.com. Before attempting a download, confirm that the file exists by running the List action against the folder that contains it. To explore the available folder structure, start your List operation at /, the root folder.

Confirm that the API Key has permission to access the path on Files.com, or switch to an API Key that does. 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 path.