High trust apps securely store and use a client secret (app secret) as shown in the diagram.
The following values for access and refresh tokens are dynamic and can change:
- Token expiration displays in the response body. Tokens created later can have different durations until they expire.
- Token lengths are not fixed.
Do not hard code access and refresh token expirations or lengths so that you can handle any future updates.
To generate an access and refresh token pair:
|1||Merchant||Log in to the merchant Clover account and install the developer’s app from the Clover App Market.|
By installing the app, the merchant authorizes the app to access the merchant’s information that the app requires.
|2||Clover UI||Redirect the merchant to the developer’s app with an authorization code.|
NOTE: If the merchant is not logged in to their Clover merchant account and they try to access to your app, Clover redirects the merchant to log in to their merchant account and back to your app.
|3||Developer app||Request an access- and refresh-token pair.|
Send a POST request to
If you do not need a refresh token, set the query parameter
See When refresh tokens are not needed for more information.
|4||Clover backend||Return an access and refresh token pair.|
Sample response body
Expiration dates are represented as Unix timestamps.
See Sandbox and production environments URLs about which URLs to use in the requests.
Updated 25 days ago