Learn more
 

Ready to get started?

Connect to live data from Coinbase with the API Driver

Connect to Coinbase

In this article

Related articles

Pipe Coinbase Data to CSV in PowerShell


Use standard PowerShell cmdlets to access Coinbase tables.

The CData Cmdlets Module for Coinbase is a standard PowerShell module offering straightforward integration with Coinbase. Below, you will find examples of using our API Cmdlets with native PowerShell cmdlets.

Creating a Connection to Your Coinbase Data

Start by setting the Profile connection property to the location of the Coinbase Profile on disk (e.g. C:\profiles\Coinbase.apip). Next, set the ProfileSettings connection property to the connection string for Coinbase (see below).

Coinbase API Profile Settings

Coinbase uses OAuth-based authentication.

First you need to register an OAuth app with Coinbase. This is done from your account under 'Settings' > 'API Access' > 'New OAuth2 Application'.

After setting the following connection properties, you are ready to connect:

  • AuthScheme: Set this to OAuth.
  • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to manage the process to obtain the OAuthAccessToken.
  • OAuthClientId: Set this to the ClientID that is specified in you app settings.
  • OAuthClientSecret: Set this to the ClientSecret that is specified in you app settings.
  • CallbackURL: Set this to the Redirect URI you specified in your app settings. 

$conn = Connect-API  -Profile "$Profile" -Authscheme "$Authscheme" -OAuthClientId "$OAuthClientId" -OAuthClientSecret "$OAuthClientSecret" -CallbackUrl "$CallbackUrl"

Selecting Data

Follow the steps below to retrieve data from the Deposits table and pipe the result into to a CSV file: 

Select-API -Connection $conn -Table Deposits | Select -Property * -ExcludeProperty Connection,Table,Columns | Export-Csv -Path c:\myDepositsData.csv -NoTypeInformation

You will notice that we piped the results from Select-API into a Select-Object cmdlet and excluded some properties before piping them into an Export-Csv cmdlet. We do this because the CData Cmdlets append Connection, Table, and Columns information onto each "row" in the result set, and we do not necessarily want that information in our CSV file.

The Connection, Table, and Columns are appended to the results in order to facilitate piping results from one of the CData Cmdlets directly into another one.