Transferring Refresh Token to Zoho Reports

The 2018 releases of Zoho Reports allow you to retrieve data using a URL with a mix of parameters specified as:

•Headers

•GET parameters

•POST parameters

All three categories of parameters are handled by the Zoho backend. However, a number of non-industry standard restrictions apply:

•The parameter value may not contain an exclamation mark ('!').

•The parameter value length may not exceed 240 characters.

Specification of a refresh token such as for Facebook or Exact Online is there not possible in general; they can be up to 1.000 characters and most of them contain an exclamation mark.

As a workaround, you can transport the refresh token to Data Access Point directly from Zoho using one of the following workarounds:

•When no exclamation mark is present in your refresh token: split the value for the X-Refresh-Token into multiple parts (at most 10). Provide the values by adding a header "X-Refresh-Token-Part" plus a number from 1 to 10 to the list of parameters and assign each one a piece of the refresh token. The resulting parameters will be named "X-Refresh-Token-Part1", "X-Refresh-Token-Part2", etc.

•When an exclamation mark is present in your refresh token: base64 encode the refresh token and split the base64 encoded value into multiple parts (at most 10). Provide the values by adding a header "X-Refresh-Token-Part" plus a number from 1 to 10, plus a prefix "-Base64" to the list of parameters and assign each one a piece of the refresh token. The resulting parameters will be named "X-Refresh-Token-Part1-Base64", "X-Refresh-Token-Part2-Base64", etc.

On reception, the parts will be assembled together and considered as follows to be used as a refresh token:

•When a X-Refresh-Token header or parameter is present, it will be preferred.

•When a non-base64 encoded value is present, that one will be used.

•Otherwise, the value provided by base64 encoding will be used as a refresh token.