Requesting a Transaction with OAuth 2.0
Once your application has requested and received an OAuth access token, it can use the access token to authenticate itself while requesting transactions. The following points illustrate use-cases that require authentication and give sample code to illustrate using the OAuth access token to provide that authentication.
Using a Data Query or Embedding a Chart
Until Zoomdata 2.2, the only possible means of authenticating a client was to use
Zoomdata's source-based security key
. Starting in version 2.2, Zoomdata allows its
security configuration object
to contain either a source-based security key or an OAuth access token, but not both. In the example above, the security configuration object is associated with the
key using the variable name
. The example below shows a security configuration object that uses an OAuth token rather than a Zoomdata security key.
You can naturally use
or the library of your choice to request a transaction using OAuth 2.0. For example:
https://yourserver/pathis the DNS and path for your Zoomdata server, using the correct protocol.
users/123456789is replaced with the method and parameters that you wish to use
Authorizationparameter contains your own access token
Was this topic helpful?