TLS
To protect data in transit, connections to the APIs must use TLS 1.2 as the minimum version.
If the client proposes unsupported cipher suites, the connection will not be established.
What happens if my client is not compatible
If your client or environment uses older ciphers or TLS versions below 1.2, the connection will be rejected before reaching the APIs.
Typical errors are TLS handshake failures (for example SSL handshake failed, TLSV1_ALERT_PROTOCOL_VERSION, or similar messages depending on your language/runtime).
How to verify compatibility
You can test TLS connectivity to the server with one of these methods:
Command line (curl)
curl -v https://api.giponext.it/swagger/docs/v2 2>&1 | grep "SSL connection"If the connection succeeds, you will see a line similar to:
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384If it fails, you will see a handshake error.
Command line (openssl)
openssl s_client -connect api.giponext.it:443 -tls1_2If the connection succeeds, you will see certificate details and the negotiated cipher. If it fails, you will receive a handshake error.
Notes by language/framework
| Language / Runtime | Notes |
|---|---|
| .NET Framework 4.8 | TLS 1.2 is supported but may not be enabled by default. Add ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12; at startup. |
| .NET 6+ | TLS 1.2+ is the default. No configuration needed. |
| Java 8+ | TLS 1.2 is supported. With Java 8, verify it is enabled (it may not be the default on very old versions). From Java 11 it is the default. |
| Python (requests) | Uses the operating system TLS stack. On modern systems no additional configuration is needed. If you use an older environment, update OpenSSL. |
| Node.js 12+ | TLS 1.2+ is the default. No configuration needed. |
Next steps
- Error handling — how to interpret HTTP errors
- Rate limiting — request limits