Can I use Server Side Scripts?

Before you can use server side scripts (either scheduled using the FileMaker Server Admin Console or via Perform Script on Server) you will first need to perform the initial authentication to generate the access and refresh tokens. The scripts will handle refreshing these if they have expired.

These tokens will be used to authenticate with QuickBooks Online from then on – you won’t be required to authenticate with the QuickBooks Online API via the FileMaker Web Viewer unless your Refresh Token expires. Access Tokens are valid for 60 minutes (we keep track of this in the Expires At field) and can be refreshed automatically using the Refresh Token. Refresh Tokens are valid for 100 days: if you don’t refresh your access token within 100 days you will need to click the Authenticate button and reauthorise the app.

As long as you are making a request to the QuickBooks Online API at least once every 100 days your Refresh Token will not expire, which would cause you to have to go through the Authentication process again. If you are worried about the Refresh Token expiring you can schedule the QuickBooks Authentication - OAuth 2.0 Refresh Access Token FileMaker script to be performed on a schedule (e.g. every 30 days) to ensure the Refresh Token does not expire.

You can get more information on the QuickBooks Online access tokens and refresh tokens expiration periods here.

Don’t forget to also ensure that all script steps are server compatible.