Question

API calls producing 404 "repository not found" errors when attempting to call a repository

Laserfiche Cloud Laserfiche API Integrations

Updated February 27, 2024

asked on February 23, 2024

Im using Postman and would like to call a repository with the POST Folder/Import request as documented here: Laserfiche Repository API

The problem Im having is that although I managed to get the format correctly and authenticating, it then gives this error:

I've double checked the entry ID and repository ID and they seem valid to other application so Im wondering whats wrong with the API call itself

I would also like to mention that the ultimate goal is to use this in power automate to make a sharepoint integration demo and these results are reproducible there as well.

0 0

Answer

SELECTED ANSWER

replied on February 27, 2024

To troubleshoot, I would first try to get the list of repositories using Swagger. Depending on your region Account:

2 0

Replies

replied on February 23, 2024

Nicholas,

Could you share the actual request from Postman you are making to the API (without any sensitive information)? Also, I'd recommend checking out our Guide on importing documents if you haven't already.

Andrew

0 0

View 2 previous replies

replied on February 26, 2024 • Show version history

Im using this request:

with Body (in form-data format):

and the entry ID points to a folder on the repository.

I've also tried tinkering with the body "request" portion but the only thing that really seems to make a difference is whether or not it has a "name" field to validate the JSON correctly

0 0

replied on February 27, 2024

If this is a "Service Application" in Developer Console, make sure that the corresponding Service Principal is allowed access to the repository:

0 0

replied on February 27, 2024

Yes this is configured for full rights:

0 0

SELECTED ANSWER

replied on February 27, 2024

To troubleshoot, I would first try to get the list of repositories using Swagger. Depending on your region Account:

2 0

replied on February 27, 2024

Thanks, although we are based in Canada it appears to have made a .com extension so that threw me off for a while. changing the extension to .com fixed the problem.

0 0

You are not allowed to follow up in this post.

Question

Question

API calls producing 404 "repository not found" errors when attempting to call a repository

Answer

Replies

Sign in to reply to this post.