Home Sign in

Developer Quickstart

Flow

  1. A user gets a SETUP token from the SimpleFIN server.
  2. The user gives the SETUP token to an application.
  3. The application sends the SETUP token to the SimpleFIN server and receives an ACCESS token in return.
  4. The application uses the ACCESS token to get the user's transaction data from the SimpleFIN server.
  5. At any point, the user can disable the ACCESS token.

Why?

The SimpleFIN Bridge makes it easy to get transaction data from your bank, without having to worry about how to securely store your credentials (or your customer's credentials). To get your transaction data, do this:


1. Generate a SETUP Token

Go here to generate tokens: https://bridge.simplefin.org/simplefin/create (Send other people here, too).

For testing, here's an already-generated sample token:

aHR0cHM6Ly9icmlkZ2Uuc2ltcGxlZmluLm9yZy9zaW1wbGVmaW4vY2xhaW0vZGVtbw==

2. Exchange a SETUP token for an ACCESS token

As per the spec, base64-decode the token to get a URL, then issue a POST to that URL. Here's how you'd do that in bash:

CLAIM_URL=$(echo aHR0cHM6Ly9icmlkZ2Uuc2ltcGxlZmluLm9yZy9zaW1wbGVmaW4vY2xhaW0vZGVtbw== | base64 -D)
ACCESS_URL=$(curl -X POST $CLAIM_URL)

Note that the demo Setup Token can be used repeatedly, but real Setup Tokens can only be used once. So hang on to that ACCESS_URL if you want to reuse it.

3. Use the ACCESS token to get some data

Make an HTTP GET request to the <access_url>/accounts with Basic Auth credentials. Here's how you'd do that in bash:

curl ${ACCESS_URL}/accounts


For example

This Python script (which requires the Requests library) will prompt for a token (the thing in the box above) then fetch and print the latest sample transaction data.