Several APIs are subject to returning pagination results. Those APIs are the following:

• Payments : GET /payments and GET /settlements
• Accounts : GET /transactions

Payments

PIS APIs are more flexible as these are provided directly by Fintecture.

The available feature is to be able to navigate through using the next, self page links found at the end of the JSON provided by the bank. The meta block also includes the totalItems and totalPages.

{
    "meta": {
        totalItems: 2501,
        totalPages: 26
    },
    "data": {},
    "links": {
        "next": "https://api.fintecture.com/pis/v2/payments?page[number]=2", 
        "self": "https://api.fintecture.com/pis/v2/payments?page[number]=1"
    }
}

The following filters are available:

• page[number]: the page number
• page[size]: the amount of item returned on a page (default: 100)

Accounts

AIS APIs follow the same indexing as provides the banks. Most banks don't support pagination so all the results will be returned as a single page. As the pagination logic is based on what the bank returns, the control on pagination is limited.

The available feature is to be able to navigate through using the next, self page links found at the end of the JSON provided by the bank.

{
    "meta": {},
    "data": [{},{}],
    "links": {
        "next": "https://api.fintecture.com/ais/v1/.../transactions?page[number]=2", 
        "self": "https://api.fintecture.com/ais/v1/.../transactions?page[number]=1"
    }
}

The following filters are available:

• page[cursor]: the page cursor ID
• page[number]: the page number

💡 Note

page[cursor] or page[number] depend on the bank's pagination format