News
Recent
Temporary technical issues with initiating foreign transfers | November 13th, 2025
We kindly inform you, that due to maintenance work planned by the Bank that will take place on the 13th of November 2025 between 7:00 AM and 6:00 PM, there may be temporary technical issues with initiating foreign transfers under our API production environment.
Planned service downtime due to time change | October 25-26, 2025
We kindly inform you that due to the scheduled switch from daylight saving time to standard time, a temporary unavailability of services will occur. The downtime will begin on Saturday, October 25th, 2025 at 11:00 PM and will last until Sunday, October 26th, 2025 at 6:00 AM. During this time, access to the production environment of our API services may be limited or unavailable. We apologize for any inconvenience and appreciate your understanding.
Previous
Changes to Open API production environment // 28.01.2020
We would like to inform you that we will introduce additional changes to our Open API production environment.
Therefore our API will be unavailable for just an hour from 11.00 am to 12:00 am on January 28th, 2020.
What’s new:
Deployment date: January 28, 2020
Change No. 001
Change description: The getConfirmationOfFunds service will accept the value utf-8 in Accept-Charset header. (was only UTF-8).
Change impact: no impact on TPPs
Change No. 002
Change description: If you send the request message for tax service, you have to set the full year in field ‘year’ (is optional)
Change impact: after this date, only the full-year value will be allowed in the field year
Change No. 003
Change description: The transfer for individual tax account will be forbidden for all transfer services except tax service.
Change impact: No technical impact. The transfer for individual tax account will be forbidden for all transfer services except tax service.
Change No. 004
Change description: If you send the request message, you have to change data in fields sendDate and scopeTimeLimit. The acceptable value of a string representing the given date in these fields will be in the ISO 8601 format according to universal time in the form of YYYY-MM-DDTHH:mm:ss.sssZ
Change impact: after this date the date in fields sendDate and scopeTimeLimit in other pattern than YYYY-MM-DDTHH:mm:ss.sssZ will be forbidden.
Sandbox - what's new? // January
Following the issues reported by our community, we introduce a couple of changes to our developer's portal.
What’s new:
Deployment date: January 16, 2020
Change No. 001
Change description: The getConfirmationOfFunds service will accept the value utf-8 in Accept-Charset header. (was only UTF-8).
Change impact: no impact on TPPs
Change No. 002
Change description: If you send the request message for tax service, you have to set the full year in field ‘year’ (is optional)
Change impact: after this date, only the full-year value will be allowed in the field year
Change No. 003
Change description: The transfer for individual tax account will be forbidden for all transfer services except tax service.
Change impact: No technical impact. The transfer for individual tax account will be forbidden for all transfer services except tax service.
If you need any additional information don't hesitate to contact us: developer@alior.pl.
Unavailability of API services | January 8th/9th, 2021
We kindly inform you that due to maintenance work planned by the Bank some of the services provided under the API production
environment will be unavailable on the night between 8 and 9 of January 2021 from 11.00 pm until 8.00 am.
Unavailability of API services | January 8th/9th, 2021
We kindly inform you that due to maintenance work planned by the Bank some of the services provided under the API production
environment will be unavailable on the night between 8 and 9 of January 2021 from 11.00 pm until 8.00 am.
Sandbox - what's new?
What’s new?
Change No. 001
Change description: If you send the request message, you have to change data in fields sendDate and scopeTimeLimit. The acceptable value of a string representing the given date in these fields will be in the ISO 8601 format according to universal time in the form of YYYY-MM-DDTHH:mm:ss.sssZ
Change impact: after this date the date in fields sendDate and scopeTimeLimit in other pattern than YYYY-MM-DDTHH:mm:ss.sssZ will be forbidden.
Change No. 002
Change description: The getTransactionsDone response will be enriched with simple name and postal address data. The fields sender and recipient could have new values when are available for the customer.
Change impact: no impact on TPPs.
Change No. 003
Change description: The getTransactionDetails response will be enriched with simple name and postal address data. The fields sender and recipient could have new values when are available for the customer.
Change impact: no impact on TPPs
If you need any additional information please do not hesitate to contact us