Thanks, that's helpful info.

Per the Creating an OAuth Service App for the Laserfiche API guide under Register your Service App in the Developer Console (5):

1. On the Authentication tab, create a new Access Key. There are two types of Access Keys you can create for the client credentials flow.
   • Choose create a public access key if the service app uses the Laserfiche API client libraries or is capable of generating an HMAC client credential.

   • Choose create a long-lasting authorization key if the service app does not have the capabilities of generating an HMAC client credential. This option is intended for low-code tools that require a static secret to connect to Laserfiche APIs.

Double check that you're using the appropriate Access Key type for this integration.

Then under Request an Access Token (2), it says:

For service applications, no refresh token will be returned. When the access token expires, the service application will need to start the client credentials flow again to get a new access token.

So while the Laserfiche Web API does not have a refresh token auth flow, you should not have to manually "reauthorize the connection" every few hours. When the current access token is expired, instead of trying to use a refresh token, Celigo should "start the client credentials flow again to get a new access token".

As I'm not familiar with Celigo's specific functionalities, I can't provide guidance on how specifically to implement that logic there.

Hope that helps.