March 2026 brings extended capabilities for financial data access, webhook monitoring, and granular permissions configuration.

Auth Links Validity ExtendedUpdate

Auth Links now remain valid for 30 days, allowing users to link and share data from multiple accounts across financial institutions within this period. Links expire automatically after 30 days or once users complete the disclosure flow.

  • Auth Link Expiry: 30 days or upon disclosure flow completion
  • Supported Actions: Link multiple accounts, share data with multiple institutions

Use Cases: Enable longer self-service financial data capture, reduce repeated consent requests, and allow multi-account linking in a single window.

Webhook Stats EndpointNew

The new GET /notifications/webhooks/{webhookId}/stats endpoint provides real-time monitoring of webhook delivery. Track performance and troubleshoot delivery issues directly through the API.

  • Endpoint: GET /notifications/webhooks/{webhookId}/stats
  • Response: Returns delivery status, success/failure counts, and timestamps

Use Cases: Monitor webhook success rates, identify failures, and ensure timely notifications for financial events.

Expanded Permission SetsUpdate

Permission sets now support additional endpoints across Events, Merchants, Reports, Users, Enrich, and Webhooks categories, allowing partners to enable or disable access via the Dashboard to prevent unexpected 403 errors.

  • Events & Jobs: GET /events/{eventId}, POST /jobs/{jobId}/mfa
  • Merchants: GET /merchants, GET /merchants/{merchantId}
  • Reports: GET /reports/types/{reportTypeId}, DELETE /reports/{reportId}, GET /reports/{reportId}/transactions
  • Users: POST /users/{userId}/connections/{connectionId}/purge, GET /users/{userId}/identities, POST /users/{userId}/insights/expense-ratio
  • Enrich: GET/POST /enrich/jobs, GET /enrich/jobs/{id}
  • Webhooks: GET /notifications/webhooks/{webhookId}/stats

Use Cases: Control access to sensitive endpoints, manage user-level permissions, and reduce API errors due to insufficient permissions.

These updates in March enhance user access, monitoring, and control across Basiq’s APIs, giving partners more flexibility and insight into their integrations.

🆕 Business Affordability API Now Live

📄 Documentation: Business Affordability API Docs

We’re excited to launch the Business Affordability Report API, providing partners with deep insights into the financial health of business entities—whether sole traders or large enterprises.

What’s Included:

  • Brand new Business Affordability Report API
  • Dashboard enhancements on the Reports page (now live in production)

This API builds on our Consumer Affordability foundation and supports smarter, faster, and more inclusive B2B lending through consent-based access to business financial data.


⚠️ New Error Message for Missing Consent

We’ve introduced a new 400 Bad Request error for Classic Affordability and Insight Reports, shown only when:

  • A consent has been revoked or expired, and
  • Core has not yet completed user data deletion

Error message: 400 Bad request – user doesn't have an active consent

📝 Note:
This should be rare, but may occur if a partner attempts to create a report immediately after consent is revoked and before deletion finalises.


🧾 Developer Hub Footer & Legal Disclaimer Update

What’s New:

  • ABN details for Basiq & Cuscal
  • CDR accreditation number: ADRBNK000208
  • Clarification that Basiq is not an Authorised Deposit-Taking Institution

These updates improve clarity, legal compliance, and transparency across our platforms. Big thanks to Legal, Brand, and Product for the collaboration!

We’ve rolled out some exciting updates:

Income and Expense Report subtypes

  • You can now use the Reports API to generate an Income or Expense reportSubType
  • This will create a report with only Income or only Expense related Metrics and Groups
  • Depending on the amount of transactions, a report may be generated up to 40% faster 🏎️
  • You can also choose to include specific Metrics and Groups by specifying their IDs in the request payload

Enhancements to the Consent Extend and Reauthorise flow

  • To better align with CDR CX guidelines, we have updated the user experience when a User is Extending or Reauthorising their Consent
  • Now -- prior to Extending or redirecting the User to their bank, Basiq will display the ongoing Consent details
  • This ensures the Users are fully aware of the terms before making any changes


Stay Updated 📢

If you have any questions or need further assistance, don't hesitate to reach out to our support team.


Feb'25 - API Updates

by Ashman Malik

🚀 Business Affordability Report is Here! 📊🎉

📢 New Report Release: Business Affordability Report

🚀 What’s New?

  • New Report Type: BUS_AFFOR_01 is now available.
  • Tailored for Businesses: Built on the CON_AFFOR_01 structure but optimized for business and organisational assessment.
  • Automated Date Handling: toDate() is automatically set to the current date for accuracy in balance calculations.
  • Multiple Formats: Available in both JSON and PDF.
  • Enablement: Contact support to activate this report type for your account.

🔍 This update enhances affordability assessments for businesses, providing structured, standardised insights.

Stay Updated 📣

We’ve rolled out some exciting updates:

Customise UI and Consent UI Updates

  • Improved Data Retention Controls:

    • Updated label from "Retain de-identified data by default" to "Ask to retain de-identified data".
    • Enhanced UI and disclaimers for better transparency in consent management.
    • Users now have clearer options to manage their data retention preferences.
  • Consent UI Enhancements:

    • Updated messaging to reflect that data will be deleted after the consent period.
    • Improved toggle behavior to better reflect user choices for retaining de-identified data.
    • Added additional info below the toggle to provide more clarity on how de-identified data is handled.
  • Better Customisation Experience:

    • Removed dependency between "Retain consumer data" and "Retain de-identified data" options.
    • Improved policy-based logic for displaying and managing data retention settings.

Mandatory "Manage Consent URL" for CDR Applications

  • New Requirement for CDR-Accredited Applications:
    • "Manage Consent URL" is now mandatory for applications with CDR accreditation.
    • Applications without CDR accreditation remain unaffected.
  • We have published a guide for partners on how to integrate consent management policy.


Stay Updated 📣