JavaScript is required to view this page
Getting Started with Blink Data

Using an AI coding assistant? Connect it to the BlinkPay MCP server, which has all of this documentation and the API schemas.

Quick Start

Get started with Blink Data in minutes:

# Authenticate
curl -X POST https://sandbox.data.blinkpay.co.nz/oauth2/token \
  -d "client_id=YOUR_ID&client_secret=YOUR_SECRET&grant_type=client_credentials"

# Create consent
curl -X POST https://sandbox.data.blinkpay.co.nz/v1/consents \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "flow": {
      "detail": {
        "type": "gateway",
        "redirect_uri": "https://yourapp.com/callback"
      }
    },
    "permissions": ["ReadAccounts", "ReadBalances", "ReadTransactions"],
    "expiration_date_time": "2026-12-31T23:59:59+13:00"
  }'

Environment URLs

The Blink Data base URL for each environment, with its token endpoint. API paths sit under /v1; the token endpoint sits at the host root.

EnvironmentBase URLToken endpoint
Sandboxhttps://sandbox.data.blinkpay.co.nzPOST https://sandbox.data.blinkpay.co.nz/oauth2/token
Productionhttps://data.blinkpay.co.nzPOST https://data.blinkpay.co.nz/oauth2/token

In the sandbox, use the test bank PNZ; the production banks (ANZ, ASB, BNZ, Westpac, Kiwibank and NZHL) are used in production. See Sandbox and Production Banks.

Choose Your Integration Path

Let BlinkPay handle the bank selection and authentication UI. Customer selects their bank and authentication method through our hosted gateway.

Learn more about Gateway Flow →

Redirect Flow

Direct browser-based flow where customers authenticate with their bank and return to your site.

Learn more about Redirect Flow →

Decoupled Flow

Customer authorises on a different device or at a different time via their banking app.

Learn more about Decoupled Flow →

Data Access APIs

All Data APIs are documented in the comprehensive Data Retrieval guide:

Available APIs

  • Accounts API - Get list of customer accounts including account numbers, types, names, and currencies
  • Balances API - Access current and available balances for customer accounts with timestamps
  • Transactions API - Retrieve transaction history with detailed payee information and filtering options
  • Statements API - Download account statements (availability varies by bank, most support at least 2 years)
  • Party API - Get account holder information including name and contact details

Explore Data Retrieval Guide →

Use Cases

Personal Finance Apps

Aggregate accounts from multiple banks into a single view.

Lending & Credit Assessment

Verify income and assess creditworthiness using actual bank data.

Accounting Software

Automate bank reconciliation and transaction categorisation.

Budgeting Tools

Track spending patterns and provide insights.

Wealth Management

Provide holistic financial overview across institutions.

What You'll Need

Prerequisites

Integration Standards

Before you go live, read Credential and Integration Security for how to store credentials and handle outcomes safely, and, if you use the redirect or decoupled flow directly rather than the Gateway, Consent Experience for Direct Flows for what your consent screens must show.

Support

View all support resources →

Next Steps

  1. Understand the basics - Learn about Blink Data architecture
  2. Review bank coverage - See which features each bank supports
  3. Follow the quick start guide - Create your first consent in minutes
  4. Explore authentication flows - Choose the right flow for your use case