ℹ️This change was deployed on 03.06.2025.
The following information requires action from your technical personnel to ensure continuous operation of your integration to our system. Please forward the information given accordingly.
As with our public sites, we intend to deprecate all API communication via TLS 1.0 and 1.1. This step is needed to keep your data safe with the highest levels of security and compliance. If your API client uses TLS 1.0 or 1.1, please update it to TLS 1.2 or 1.3 before this date to avoid disruptions.
Your action is required, we support you!
To make sure your API client remains functional, we already rolled out the new security policy on our preview API. We have created a test user for you there, so you can make a test request against it with your production client.
Endpoint: [https://api-preview.refurbed.com/refb.merchant.v1.CurrencyService/ListCurrencies](https://api-preview.refurbed.com/refb.merchant.v1.CurrencyService/ListCurrencies')
Authorization: Plain *******
curl example:
curl -v -X POST \ '<https://api-preview.refurbed.com/refb.merchant.v1.CurrencyService/ListCurrencies>' \ -header 'Accept: /' \ -header 'Authorization: Plain 26693b73-51d3-4d48-a8b1-a28976af0ca7' \ -header 'Content-Type: application/json'
⚠️ It is important that you run a test call with the used library from your client directly e.g. (PHP) curl, (python) requests etc. to make sure the connection will continue working.
If the request was successful, there is no further action to be taken and your API client is ready.
If the request failed, it is most likely due to an outdated client/library. In this case, we would advise you to update it to allow communication via TLS 1.2 and higher.
If you run into unconditional problems, you can contact us (integrations@refurbed.com) and provide us with any output of the failed connection (e.g. from the curl call above).