# Fiskil Documentation

> This file lists all documentation pages to help AI tools understand the documentation structure.

## Data Api
Connect to consumer banking and energy data with consent.

### Guides
_Step-by-step guides and documentation_

- [API Versioning](/data-api/guides/core-concepts/versioning): How Fiskil Data API versions work, how to select one, and how upgrades happen
- [Auth Sessions](/data-api/guides/core-concepts/auth-sessions): Temporary sessions used to initiate Fiskil's consent flow
- [Authentication](/data-api/guides/getting-started/authentication): Learn how to authenticate with the Fiskil API
- [Banking](/data-api/guides/data-domains/banking): Fiskil's Banking APIs provide secure, consent-driven access to a customer's financial data, retrieved directly from their connected bank accounts.
- [Banking - Business Accounts](/data-api/guides/help-center/business-accounts): Guidance and resources for sharing data from business banking accounts.
- [Best Practices](/data-api/guides/resources/best-practices): Recommendations for building robust Fiskil integrations
- [Configure Microsoft (Entra ID) as a SSO Provider](/data-api/guides/account-access/sso-login/microsoft): Configure Single Sign-On authentication for your team to access the Fiskil Console using your existing Microsoft identity provider.
- [Consents](/data-api/guides/core-concepts/consents): Understanding how data sharing consent works in Fiskil
- [End Users](/data-api/guides/core-concepts/end-users): Understanding the core user entity in the Fiskil platform
- [Energy - Business Accounts](/data-api/guides/help-center/energy-accounts): Guidance and resources for connecting business energy accounts and nominated representatives.
- [Energy Data](/data-api/guides/data-domains/energy): Fiskil's Energy APIs allow your application to securely access utility account data authorised by the customer through a linked energy provider.
- [Flow Overview](/data-api/guides/link-widget/flow-overview): Understanding the steps in the Fiskil consent flow
- [Go Live Checklist](/data-api/guides/resources/go-live-checklist): Everything you need to complete before launching your Fiskil integration in production
- [Identity Data](/data-api/guides/data-domains/identity): Fiskil provides access to verified identity information associated with a user's connected accounts.
- [Income](/data-api/guides/data-domains/income): Fiskil's Income API provides structured insights into consumer income using enriched transaction data.
- [Integrating the Link SDK](/data-api/guides/link-widget/integrating-the-link-sdk): Step-by-step guide to integrate the Fiskil Link SDK
- [Introduction](/data-api/guides/link-widget): Embed Fiskil's consent flow inside your application
- [MCP Server](/data-api/guides/ai-tools/mcp): Connect AI tools directly to Fiskil documentation using Model Context Protocol
- [Migrating to Fiskil APIs](/data-api/guides/help-center/migrations): Plan and execute a phased migration to Fiskil with minimal risk and disruption.
- [Mobile Integration](/data-api/guides/resources/mobile-integration): Integrate the Fiskil consent flow into iOS and Android apps using the Link SDK in a WebView
- [Monitoring & Logs](/data-api/guides/account-access/monitoring-and-logs): Understand how to monitor webhook deliveries and implement logging practices to keep your integration reliable.
- [Overview](/data-api/guides/ai-tools): Use AI assistants to build Fiskil integrations faster
- [Overview](/data-api/guides/core-concepts/overview): API protocols, headers, and resources
- [Quick Start](/data-api/guides/getting-started/quick-start): Get up and running with Fiskil quickly
- [Renew Consents](/data-api/guides/resources/renew-consents): A playbook for helping customers renew Data API consents before they expire.
- [Security](/data-api/guides/account-access/security): Fiskil provides multiple layers of security to protect your Console account and manage access to sensitive data.
- [SSO Logins](/data-api/guides/account-access/sso-login): Enable Single Sign-On authentication for your team to access the Fiskil Console using your existing identity provider.
- [Start Exploring](/data-api/guides/getting-started/start-exploring): Essential information to kick off with Fiskil
- [Team & Roles](/data-api/guides/account-access/team-and-roles): Manage workspace access by inviting team members and assigning role-based permissions.
- [Testing](/data-api/guides/core-concepts/testing): Test your Fiskil integration with the Sandbox environment
- [Troubleshooting](/data-api/guides/support/troubleshooting): Troubleshoot common integration issues and find the right support resources.
- [Webhooks](/data-api/guides/core-concepts/webhooks): Receive real-time updates from Fiskil directly to your application

### Api Reference
_API endpoint reference documentation_

- [Accounts](/data-api/api-reference/accounts): List and retrieve bank account information from the Fiskil API.
- [Auth Session](/data-api/api-reference/auth-session): Create authorization sessions for end users to grant data access.
- [Authentication](/data-api/api-reference/authentication): Learn how to authenticate your API requests with Fiskil.
- [Balance](/data-api/api-reference/balance): Get bank account balances from the Fiskil API.
- [Billing](/data-api/api-reference/billing): Get billing information from the Fiskil API.
- [Concessions](/data-api/api-reference/concessions): Get concession information from the Fiskil API.
- [Consents](/data-api/api-reference/consents): View and manage data sharing consents in the Fiskil API.
- [Create auth session](/data-api/api-reference/create-auth-session): Create an auth session before auth process.
- [Create end user](/data-api/api-reference/create-end-user): Creates a new end user
- [Delete end user](/data-api/api-reference/delete-end-user): Allows a client to delete an end user
- [DER](/data-api/api-reference/der): Get Distributed Energy Resources (DER) data from the Fiskil API.
- [Direct Debits](/data-api/api-reference/direct-debits): Get direct debit information from the Fiskil API.
- [End User](/data-api/api-reference/end-user): Manage end users in your Fiskil application.
- [Energy Accounts](/data-api/api-reference/energy-accounts): List and retrieve energy account information from the Fiskil API.
- [Energy Balances](/data-api/api-reference/energy-balances): Get energy account balances from the Fiskil API.
- [Errors](/data-api/api-reference/errors): Understanding error responses from the Fiskil API.
- [Get Balances](/data-api/api-reference/getBankingBalances): Returns list of banking account balances available under the authorised consent
- [Get Banking Transaction Refresh](/data-api/api-reference/getBankingTransactionRefresh): Query the status of a previously submitted asynchronous banking transaction refresh.
- [Get billing transactions](/data-api/api-reference/getEnergyBilling): Returns billing transactions for all accounts authorised by the end user
- [Get customer details](/data-api/api-reference/getCustomerIdentity): Returns detailed information about the consumer identities from the most recent consent
- [Get Data Freshness](/data-api/api-reference/getDataFreshness): Returns freshness information for datasets such as banking.transactions
- [Get direct debits](/data-api/api-reference/getDirectDebits): Returns list of banking account direct debits available under the authorised consent
- [Get end user by id](/data-api/api-reference/get-end-user-by-id): Finds an end user by end user id
- [Get energy plan details](/data-api/api-reference/getEnergyPlanDetail): Get details of an energy plan using the plan's ID
- [Get institution by id](/data-api/api-reference/get-institution-by-id): Get institution by id
- [Get Payees](/data-api/api-reference/getBankingPayees): Returns list of banking payees available under the authorised consent
- [Get product details](/data-api/api-reference/getBankingProductDetailV2): Returns detailed information about a banking product
- [Get Scheduled Payments](/data-api/api-reference/getScheduledPayments): Returns list of banking scheduled payments available under the authorised consent
- [Get service points](/data-api/api-reference/getEnergyServicePoints): Returns detailed information about service points owned by the end user that has authorised the current session
- [Get Transactions](/data-api/api-reference/getBankingTransactionsV2): Returns list of banking transactions available under the authorised consent. For data freshness details, see /v1/data-freshness.
- [Get usage](/data-api/api-reference/getEnergyUsage): Returns usage data for all service points associated with the end user
- [Handle Accounts](/data-api/api-reference/getBankingAccountsV2): returns list of banking account Accounts available under the authorised consent
- [Handle Income](/data-api/api-reference/getBankingIncome): returns an income summary for the end-user. This is calculated over all consents associated with the end-user in real-time, and includes data from all connected bank accounts
- [Identity](/data-api/api-reference/identity): Get identity information from the Fiskil API.
- [Income](/data-api/api-reference/income): Get income data derived from transaction analysis.
- [Institutions](/data-api/api-reference/institutions): List and retrieve institution (data holder) information from the Fiskil API.
- [Introduction](/data-api/api-reference): Welcome to the Fiskil API documentation—your toolkit for seamless integration with financial and energy data.
- [Invoices](/data-api/api-reference/invoices): Get energy invoice data from the Fiskil API.
- [Linking Accounts](/data-api/api-reference/linking-accounts): Understanding the account linking flow in the Fiskil API.
- [List concessions](/data-api/api-reference/getEnergyConcessions): Returns the details of any concessions or arrangements applied to a energy accounts authorised by the end user
- [List consents](/data-api/api-reference/list-consents): List consents belonging to a client.
- [List DER (Distributed Energy Resources)](/data-api/api-reference/getEnergyDer): Obtain DER data for all service points authorised by the end user
- [List end users](/data-api/api-reference/list-end-users): List end users belonging to a client.
- [List energy account balances](/data-api/api-reference/getEnergyBalances): Returns list of energy account balances for accounts authorised by the end user
- [List energy accounts](/data-api/api-reference/getEnergyAccounts): Returns list of energy accounts belonging to the provided end user
- [List institutions by client](/data-api/api-reference/list-institutions-by-client): Gets a list of institutions a client subscribes to.
- [List invoices](/data-api/api-reference/getEnergyInvoices): Returns the invoices for all accounts authorised by the end user
- [List payment schedules](/data-api/api-reference/getEnergyPaymentSchedules): Returns the agreed payment schedule and details, if any, for energy accounts authorised by the end user.
- [List permissions](/data-api/api-reference/list-permissions): Returns a list of Fiskil permissions.
- [List Plans](/data-api/api-reference/getEnergyPlans): Obtain a list of energy plans that are offered to the market.
- [List products products](/data-api/api-reference/listBankingProducts): Returns list of banking products for a given institution
- [Override Transaction Category](/data-api/api-reference/overrideTransactionCategory): Overrides the Fiskil predicted category of a specific banking transaction.
- [Pagination](/data-api/api-reference/pagination): How to handle paginated responses from the Fiskil API.
- [Payee](/data-api/api-reference/payee): Get payee information from the Fiskil API.
- [Payment Schedule](/data-api/api-reference/payment-schedule): Get payment schedule information for energy accounts from the Fiskil API.
- [Permissions](/data-api/api-reference/permissions): Understanding data permissions and scopes in the Fiskil API.
- [Plans](/data-api/api-reference/plans): Get energy plan information from the Fiskil API.
- [Products](/data-api/api-reference/products): Get bank product information from the Fiskil API.
- [Refresh Banking Transactions](/data-api/api-reference/refreshBankingTransactions): Queues an asynchronous refresh of banking transactions for all accounts connected to the end user.
- [Revoke consent](/data-api/api-reference/revoke-consent): Allows a client to revoke a consent
- [Scheduled Payments](/data-api/api-reference/scheduled-payments): Get scheduled payment information from the Fiskil API.
- [Service Points](/data-api/api-reference/service-points): Get service point (NMI) information from the Fiskil API.
- [Update end user](/data-api/api-reference/update-end-user): Update an end user
- [Usage](/data-api/api-reference/usage): Get energy usage data from the Fiskil API.

### Changelog
_Product updates and changes_

- [Changelog](/data-api/changelog): Release notes and versioning updates for the Fiskil Data API.
- [Legacy Changelog](/data-api/changelog/legacy): Pre-reset changelog entries for the Fiskil Data API (prior to the 2026-04-07 v2.0.0 version reset).
- [Upgrade to v2](/data-api/changelog/upgrade-guide): Migration guide for upgrading the Fiskil Data API from v1 to v2
- [Upgrade to v3](/data-api/changelog/upgrade-guide-v3): Migration guide for upgrading the Fiskil Data API from v2 or v1 to v3

## Data Holder
Expose your institution's data via CDR-compliant APIs.

### Guides
_Step-by-step guides and documentation_

- [AEMO](/data-holder/guides/integrations/aemo): Connect with AEMO as a Secondary Data Holder for energy data sharing through Fiskil's managed integration.
- [API Testing](/data-holder/guides/product-portal/api-testing): Test your CDR Products endpoint directly from the Console to verify how products are exposed in staging and production.
- [Authentication & Authorization](/data-holder/guides/build/end-user-authentication): How your users authenticate and authorize data sharing.
- [Branding](/data-holder/guides/configure/branding)
- [Compliance Tools](/data-holder/guides/testing/compliance-tools): Support for validating regulated Data Provider instances against conformance requirements.
- [Configure Microsoft (Entra ID) as a SSO Provider](/data-holder/guides/security/sso-microsoft): Configure Single Sign-On authentication for your team to access the Fiskil Console using your existing Microsoft identity provider.
- [Consents](/data-holder/guides/build/consents): Manage user consents and data access permissions
- [Creating and managing products](/data-holder/guides/product-portal/creating-products): Learn how to create, edit, approve, and publish products in Product Portal.
- [Custom Domains](/data-holder/guides/configure/custom-domains)
- [External Identity Providers](/data-holder/guides/configure/external-idp): Learn how to bring your own identity provider into your Fiskil environment
- [Financial-grade API (FAPI)](/data-holder/guides/security/fapi): How Fiskil implements the FAPI 2.0 Security Profile and Message Signing profile to protect financial data sharing with mTLS, PAR, DPoP, and PKCE.
- [Firewall](/data-holder/guides/security/firewall): How Fiskil Firewall throttles data recipients, mitigates DDoS, and blocks malicious traffic before it reaches your Resource Server.
- [Frequently Asked Questions](/data-holder/guides/help/faq): Common questions about Fiskil Data Provider implementation and usage.
- [Gentrack](/data-holder/guides/integrations/gentrack): Connect with Gentrack utility platforms through Fiskil for compliant energy and utility data sharing.
- [Go Live Checklist](/data-holder/guides/go-live): Complete guide to validate your Data Provider is ready for production, including compliance requirements and data recipient onboarding.
- [Instances](/data-holder/guides/get-started/instances): Deploy and manage Data Provider instances for your environments.
- [Introduction to Data Provider](/data-holder/guides/introduction): Enable secure, user-permissioned data sharing with confidence. Fiskil handles authorization, consent flows, and compliance so you can focus on your product.
- [JWT Security](/data-holder/guides/build/jwt-security): JWT-based authentication between your Data Provider and Resource Server using JWKS and short-lived tokens.
- [Logs](/data-holder/guides/telemetry/logs): View and export Data Provider request logs via the Console or forward to your SIEM/observability tools.
- [Metrics](/data-holder/guides/telemetry/metrics): Comprehensive operational metrics tracked automatically for compliance, performance monitoring, and business insights.
- [Onboarding Clients](/data-holder/guides/configure/onboarding-clients): Invite third parties to integrate with your Data Provider
- [Overview](/data-holder/guides/configure)
- [Overview](/data-holder/guides/testing): How to test and validate your Fiskil Data Provider integration before going live.
- [Plaid](/data-holder/guides/integrations/plaid): Connect with Plaid, the leading US financial data aggregator, through Fiskil Data Provider for secure financial data sharing.
- [Quickstart](/data-holder/guides/get-started/quickstart): Ship your first Data Provider integration — from resource server to end-to-end validation — in under an hour.
- [Regulatory Reporting](/data-holder/guides/testing/regulatory-reporting): How to prepare six-monthly CDR data holder reporting using Fiskil Console Analytics.
- [Resource Server](/data-holder/guides/build/resource-server): Responsibilities, contracts, and implementation guidance for a compliant Resource Server.
- [Resource Server Settings](/data-holder/guides/configure/resource-server-settings)
- [SSO Logins](/data-holder/guides/security/sso): Enable Single Sign-On authentication for your team to access the Fiskil Console using your existing identity provider.
- [Tally Group](/data-holder/guides/integrations/tally-group): Integrate with Tally Group's energy billing platforms through Fiskil for secure customer and billing data sharing.
- [Testing in Postman](/data-holder/guides/testing/postman): Validate your integration end‑to‑end using our Postman collection, your mock users, and Request Logs.
- [What is Product Portal](/data-holder/guides/product-portal/what-is-product-portal): Learn how Product Portal helps you manage, approve, and publish compliant product data.

### Api Reference
_API endpoint reference documentation_

- [Bring Your Own Data](/data-holder/api-reference/bring-your-own-data): Share any commercial dataset through the Fiskil platform with secure, compliant data sharing infrastructure.
- [Custom Schema](/data-holder/api-reference/custom-schema): Use the power of OpenAPI to build your Open Data environment
- [Errors](/data-holder/api-reference/cdr-reference/errors): Standard error handling and status codes for CDR Resource Server integrations.
- [Fetch a customer's identity details](/data-holder/api-reference/cdr-reference/getIdentity): Get detailed information about a customers identity. This is used to construct ID
tokens. Data in the response will only be shared to clients if the client requested
the appropriate claim or scope. For details on how the values are used by clients,
refer to the Open ID Connect [standard claims](https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.5.1)

- [Fetch a customer's identity details](/data-holder/api-reference/fdx/getIdentity): Get detailed information about a customers identity. This is used to construct ID
tokens. Data in the response will only be shared to clients if the client requested
the appropriate claim or scope. For details on how the values are used by clients,
refer to the Open ID Connect [standard claims](https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.5.1)

- [Fetch a customer's identity details](/data-holder/api-reference/latam-chile/getIdentity): Get detailed information about a customers identity. This is used to construct ID
tokens. Data in the response will only be shared to clients if the client requested
the appropriate claim or scope. For details on how the values are used by clients,
refer to the Open ID Connect [standard claims](https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.5.1)

- [Fetch a customer's identity details](/data-holder/api-reference/latam-colombia/getIdentity): Get detailed information about a customers identity. This is used to construct ID
tokens. Data in the response will only be shared to clients if the client requested
the appropriate claim or scope. For details on how the values are used by clients,
refer to the Open ID Connect [standard claims](https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.5.1)

- [Fetch a customer's identity details](/data-holder/api-reference/bring-your-own-data/getIdentity): Get detailed information about a customers identity. This is used to construct ID
tokens. Data in the response will only be shared to clients if the client requested
the appropriate claim or scope. For details on how the values are used by clients,
refer to the Open ID Connect [standard claims](https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.5.1)

- [Fetch specific accounts](/data-holder/api-reference/cdr-reference/listBankingAccountsPost): Fetch accounts based on a list of IDs specified in request body. This is used to filter to authorised accounts only.
- [Fetch specific accounts](/data-holder/api-reference/fdx/getSpecificAccounts): Fetch a specified set of accounts. When a client requests all accounts, this API will be used
to filter to only the accounts that were authorized by the end user.

- [Fetch specific Energy Accounts](/data-holder/api-reference/cdr-reference/listAccountspost): Fetch the details of specific energy accounts that have been authorised by the user
- [Fiskil FDX API](/data-holder/api-reference/fdx): The Fiskil FDX API is a subset of the FDX API specification suited to most Open Finance use cases.
- [Frequently Asked Questions](/data-holder/api-reference/cdr-reference/cdr-faqs): Common questions about Consumer Data Right implementation, compliance, and operations for data holders using Fiskil.
- [Get Account Balance](/data-holder/api-reference/cdr-reference/getBalance): Obtain the balance for a single specified account
- [Get Account Balance](/data-holder/api-reference/latam-chile/getAccountBalance): Returns the current balance and historical balance entries for a specific account. Supports date range filtering via query parameters.
- [Get Account Balance](/data-holder/api-reference/latam-colombia/coGetAccountBalance): Returns the current balance and historical balance entries for a specific account. Supports date range filtering via query parameters.
- [Get Account Balances](/data-holder/api-reference/psd2/getAccountBalances): Retrieve current and available balances for a specific account. Returns balance information including currency and balance types.

- [Get Account Detail](/data-holder/api-reference/cdr-reference/getAccountDetail): Obtain detailed information on a single account.
- [Get Account Detail](/data-holder/api-reference/latam-chile/getAccount): Returns detailed information about a specific account identified by its account ID, including type, status, currency, ownership, branch, product, and conditions.
- [Get Account Detail](/data-holder/api-reference/latam-colombia/coGetAccount): Returns detailed information about a specific account identified by its account ID, including type, status, currency, ownership, branch, product, and conditions.
- [Get Account Details](/data-holder/api-reference/psd2/getAccountDetails): Retrieve detailed information for a specific account, including account metadata, product information, and account status.

- [Get account statement](/data-holder/api-reference/fdx/getAccountStatement): Get account statement PDF

- [Get Account Transactions](/data-holder/api-reference/psd2/getAccountTransactions): Retrieve transaction history for a specific account. Supports filtering by date range and pagination for large result sets.

- [Get Accounts](/data-holder/api-reference/cdr-reference/listBankingAccounts): Gets a list of accounts for a customer ID. If any account is a joint account or an organisation account the 'users' field must be populated with all related users of the energy account e.g. joint account holders, secondary users, or nominated representatives.
- [Get Accounts](/data-holder/api-reference/psd2/getAccounts): Retrieve a list of payment accounts that the customer has consented to share. This endpoint returns basic account information including account identifiers, names, and types.

- [Get Agreed Payment Schedule](/data-holder/api-reference/cdr-reference/getPaymentSchedule): Obtain the agreed payment schedule and details, if any, for a specific energy account.
Some general notes about this end point:
  * This API describes how the consumer has elected to pay for their account
  * Payments initiated by the consumer are classified as manual payments. The billing frequency is captured for manual payments. The consumer may choose to pay on a different schedule/frequency. The payment method and frequency is not captured for manual payments
  * Payments that can be initiated by the retailer, based on a consumer's preferences and permission, include payments based on a direct debit, card debit or digital wallet setup. Each of these requires a payment frequency to be provided along with other relevant fields
  * Information about payment plans related to debt repayments or arrangements due to hardship is not captured within this API

- [Get an account's contact information](/data-holder/api-reference/fdx/getAccountContact): Get contact information on the account.

- [Get asset transfer details for this account](/data-holder/api-reference/fdx/getAccountAssetTransferNetworks): Get asset transfer networks supported by an account. For example, Automated Customer Account Transfer Service (ACATS).

- [Get Balance For Energy Account](/data-holder/api-reference/cdr-reference/getBalanceForAccount): Obtain the current balance for a specific account
- [Get Balances For Specific Accounts](/data-holder/api-reference/cdr-reference/listBalancesSpecificAccounts): Obtain balances for a specified list of accounts
- [Get Balances For Specific Energy Accounts](/data-holder/api-reference/cdr-reference/listBalancesForAccounts): Obtain the current balance for a specified set of accounts
- [Get Billing For Account](/data-holder/api-reference/cdr-reference/getBillingForAccount): Obtain the billing transactions for a specific account
- [Get Billing For Specific Accounts](/data-holder/api-reference/cdr-reference/listBillingForAccounts): Obtain billing for a specified set of authorised accounts
- [Get Concessions](/data-holder/api-reference/cdr-reference/getConcessions): Obtain the details of any concessions or arrangements applied to a specific energy account
- [Get Customer (Natural Person)](/data-holder/api-reference/latam-chile/getCustomerPN): Returns personal information for a natural person (persona natural) customer, including identity details (RUT), contact information, address, occupation, income range, PEP status, and KYC status.
- [Get Customer (Natural Person)](/data-holder/api-reference/latam-colombia/coGetCustomerPN): Returns personal information for a natural person (persona natural) customer, including identity details (Cédula de Ciudadanía), contact information, address, occupation, income range, PEP status, and KYC status.
- [Get Customer Detail](/data-holder/api-reference/cdr-reference/getCustomerDetail): Obtain detailed information on the authorised customer within the current session.
- [Get Customer Information](/data-holder/api-reference/psd2/getCustomer): Retrieve basic customer information associated with the authenticated session. Used for customer identification and verification.

- [Get detailed information for a specific account](/data-holder/api-reference/fdx/getAccount): Get account balances, liabilities, and other information.

- [Get Direct Debits For Account](/data-holder/api-reference/cdr-reference/listDirectDebits): Obtain direct debit authorisations for a specific account
- [Get Direct Debits For Specific Accounts](/data-holder/api-reference/cdr-reference/listDirectDebitsSpecificAccounts): Obtain direct debit authorisations for a specified list of accounts
- [Get Energy Account Detail](/data-holder/api-reference/cdr-reference/getAccount): Obtain detailed information for a specific energy account
- [Get Energy Accounts](/data-holder/api-reference/cdr-reference/listAccounts): List all accounts available for data sharing. This will be used to support account selection during the authorisation.
- [Get Instalment Plans for Account](/data-holder/api-reference/cdr-reference/listInstalmentPlans): Obtain instalment plans for a single specified account. The response must be ordered by plan `creationDate` in descending order.

An instalment plan describes the terms of repayment for a specified loan amount such as a Buy Now, Pay Later (BNPL) purchase or a specific card transaction.

If `isInstalmentDetailAvailable` was specified as `true` for the provided `accountId` but no plans match the provided parameters, an empty array must be returned. If `isInstalmentDetailAvailable` was specified as `false` for the provided `accountId`, then the endpoint may respond with a `404 Resource Not Implemented` error.
- [Get Instalment Plans For Specific Accounts](/data-holder/api-reference/cdr-reference/listInstalmentPlansSpecificAccounts): Obtain instalment plans for a specified list of accounts. The response must be ordered by plan `creationDate` in descending order.

If instalments are not supported for any account type, the endpoint may respond with a `404 Resource Not Implemented` error.
- [Get Invoices For Account](/data-holder/api-reference/cdr-reference/getInvoicesForAccount): Obtain the invoices for a specific account
- [Get Invoices For Specific Accounts](/data-holder/api-reference/cdr-reference/listInvoicesForAccounts): Obtain invoices for a specified set of accounts
- [Get Payee Detail](/data-holder/api-reference/cdr-reference/getPayeeDetail): Obtain detailed information on a single payee.

Note that the payee sub-structure should be selected to represent the payment destination only rather than any known characteristics of the payment recipient.
- [Get Payees](/data-holder/api-reference/cdr-reference/listPayees): Obtain a list of pre-registered payees.
- [Get payment networks supported by the account](/data-holder/api-reference/fdx/getAccountPaymentNetworks): Get payment networks supported by an account, for example ACH (Automated Clearing House).

- [Get Scheduled Payments for Account](/data-holder/api-reference/cdr-reference/listScheduledPayments): Obtain scheduled, outgoing payments for a specific account
- [Get Scheduled Payments For Specific Accounts](/data-holder/api-reference/cdr-reference/listScheduledPaymentsSpecificAccounts): Obtain scheduled payments for a specified list of accounts
- [Get Transaction Detail](/data-holder/api-reference/cdr-reference/getTransactionDetail): Obtain detailed information on a transaction for a specific account
- [Get Transaction Details](/data-holder/api-reference/psd2/getTransactionDetails): Retrieve detailed information for a specific transaction, including extended transaction data and merchant information.

- [Get Transactions For Account](/data-holder/api-reference/cdr-reference/getTransactions): Obtain transactions for a specific account.

Some general notes that apply to all end points that retrieve transactions:

- Where multiple transactions are returned, transactions should be ordered according to effective date in descending order
- As the date and time for a transaction can alter depending on status and transaction type two separate date/times are included in the payload. There are still some scenarios where neither of these time stamps is available. For the purpose of filtering and ordering it is expected that the data holder will use the "effective" date/time which will be defined as:
  - Posted date/time if available, then
  - Execution date/time if available, then
  - A reasonable date/time nominated by the data holder using internal data structures
- For transaction amounts it should be assumed that a negative value indicates a reduction of the available balance on the account while a positive value indicates an increase in the available balance on the account
- For aggregated transactions (ie. groups of sub transactions reported as a single entry for the account) only the aggregated information, with as much consistent information across the subsidiary transactions as possible, is required to be shared
- [Integration Requirements](/data-holder/api-reference/cdr-reference/integration-requirements): Complete functional and non-functional requirements for integrating with Fiskil's CDR Data Provider platform.
- [Integration Requirements](/data-holder/api-reference/latam-colombia/integration-requirements): Complete functional and non-functional requirements for integrating with Fiskil's Colombian Open Finance Data Provider platform.
- [Integration Requirements](/data-holder/api-reference/latam-chile/integration-requirements): Complete functional and non-functional requirements for integrating with Fiskil's Chilean Open Finance Data Provider platform.
- [Legacy CDR Consent Flow APIs](/data-holder/api-reference/cdr-reference/legacy-auth): Deprecated APIs to support CDR consent flow prior to 2026
- [List Account Transactions](/data-holder/api-reference/latam-chile/listAccountTransactions): Returns a paginated list of transactions for a specific account. Supports date range filtering. Each transaction includes debtor/creditor details, merchant information, and card instruments.
- [List Account Transactions](/data-holder/api-reference/latam-colombia/coListAccountTransactions): Returns a paginated list of transactions for a specific account. Supports date range filtering. Each transaction includes debtor/creditor details, merchant information, and card instruments.
- [List Accounts](/data-holder/api-reference/latam-chile/listAccounts): Returns a paginated list of all accounts belonging to the authenticated customer. Each account includes details such as type, status, currency, ownership, and applicable conditions.
- [List Accounts](/data-holder/api-reference/latam-colombia/coListAccounts): Returns a paginated list of all accounts belonging to the authenticated customer. Each account includes details such as type, status, currency, ownership, and applicable conditions.
- [List accounts available for sharing](/data-holder/api-reference/cdr-reference/listAccountsAuth): Lists all accounts belonging to the customer that are available for sharing. If account selection is supported for your Data Provider, this API will be used to present the user with a list of accounts to authorize
- [List accounts available for sharing](/data-holder/api-reference/fdx/listAccountsAuth): Lists all accounts belonging to the customer that are available for sharing. If account selection is supported for your Data Provider, this API will be used to present the user with a list of accounts to authorize
- [List accounts available for sharing](/data-holder/api-reference/latam-chile/listAccountsAuth): Lists all accounts belonging to the customer that are available for sharing. If account selection is supported for your Data Provider, this API will be used to present the user with a list of accounts to authorize
- [List accounts available for sharing](/data-holder/api-reference/latam-colombia/listAccountsAuth): Lists all accounts belonging to the customer that are available for sharing. If account selection is supported for your Data Provider, this API will be used to present the user with a list of accounts to authorize
- [List accounts available for sharing](/data-holder/api-reference/bring-your-own-data/listAccountsAuth): Lists all accounts belonging to the customer that are available for sharing. If account selection is supported for your Data Provider, this API will be used to present the user with a list of accounts to authorize
- [Non-Functional Requirements](/data-holder/api-reference/cdr-reference/cdr-nfrs): Technical requirements for CDR API performance, availability, traffic thresholds, and data quality standards.
- [Search Customers by email](/data-holder/api-reference/cdr-reference/customerSearch): Used during authentication to lookup customer data based on email address. Customers will be authenticated via OTP before data sharing is authorised.
- [Search Customers by email](/data-holder/api-reference/fdx/customerSearch): Used during authentication to lookup customer data based on email address. Customers will be authenticated via OTP before data sharing is authorised.
- [Search Customers by email](/data-holder/api-reference/latam-chile/customerSearch): Used during authentication to lookup customer data based on email address. Customers will be authenticated via OTP before data sharing is authorised.
- [Search Customers by email](/data-holder/api-reference/latam-colombia/customerSearch): Used during authentication to lookup customer data based on email address. Customers will be authenticated via OTP before data sharing is authorised.
- [Search Customers by email](/data-holder/api-reference/bring-your-own-data/customerSearch): Used during authentication to lookup customer data based on email address. Customers will be authenticated via OTP before data sharing is authorised.
- [Search for account transactions](/data-holder/api-reference/fdx/searchForAccountTransactions): List all account transactions.
Fiskil always queries this endpoint using a `startTime` and an `endTime`, for example, `/accounts/{accountId}/transactions?startTime=2022-01-30&endTime=2022-05-30`,
and expects the time filters to be based on the `postedTimestamp`.

- [Search for statements](/data-holder/api-reference/fdx/searchForAccountStatements): Get account statements.

- [Servicepoint Search (AEMO)](/data-holder/api-reference/cdr-reference/servicePointSearch): Search energy customer servicepoint data by account IDs. This is only required to be implemented for Energy data holders.

### Changelog
_Product updates and changes_

- [Changelog](/data-holder/changelog): All the changes made to the documentations are listed here starting from 10-08-2023.

### Platform Api

- [Authentication](/data-holder/platform-api/authentication): Authenticate to the Platform API using client credentials to manage products programmatically.
- [Create a new product](/data-holder/platform-api/createProduct): Create a new banking product with the provided details
- [Delete a product](/data-holder/platform-api/deleteProduct): Delete a product by ID
- [Examples](/data-holder/platform-api/examples): See example payloads to manage different types of products.
- [Get a product](/data-holder/platform-api/getProduct): Get a product by ID
- [Introduction](/data-holder/platform-api/introduction): Programmatically manage your Fiskil Data Provider platform resources.
- [List consents](/data-holder/platform-api/listConsents): List consents for a team
- [List products](/data-holder/platform-api/listProducts): List products for a team
- [Update a product](/data-holder/platform-api/updateProduct): Update a product by ID

---

## Additional Resources

- [Full Documentation Text](/llms-full.txt): Complete documentation as a single file for LLM context
- [Capabilities](/skill.md): What you can build with Fiskil APIs