# curl exit code: CURLE_SSL_CONNECT_ERROR (35)

Independent and unofficial. Not affiliated with or endorsed by any broker or platform named here. Educational only: nothing here is advice, and nothing here recommends a broker or a trade.

This is the markdown version of https://openbrokerapi.com/errors/curl/35, written from the same records as that page.

Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.

As text you can copy:

```
CURLE_SSL_CONNECT_ERROR (35)
```

- Kind: Exit code
- Where you meet it: The exit status of the command
- Read from: [libcurl error codes (libcurl-errors); the exit codes section of the curl manual lists the same number](https://curl.se/libcurl/c/libcurl-errors.html#CURLESSLCONNECTERROR)
- Status: verified. Source: [curl.se](https://curl.se/libcurl/c/libcurl-errors.html#CURLESSLCONNECTERROR), checked 2026-10-09.

## What does CURLE_SSL_CONNECT_ERROR (35) mean in curl?

A problem occurred somewhere in the SSL/TLS handshake. The documentation says to read the error message, because it pinpoints the problem more closely, and that the cause could be certificates, passwords and others. The curl command line tool exits with the same number, which its manual lists under exit codes.

## What it means in trading API work

The secure connection to the API could not be set up, so no request was sent. One possible cause is an old version of curl, or of its TLS library, that cannot agree a protocol version with the server.

This part is this site's own explanation, written for people learning to call a trading API. It is not part of the source cited above and it describes no particular broker.

## What should I do about CURLE_SSL_CONNECT_ERROR (35)?

Run the command again with the verbose option and read the message. Update curl. Do not use the insecure option to get past it.

This page is an independent explanation in plain words. The definition itself is in [the source it was read from](https://curl.se/libcurl/c/libcurl-errors.html#CURLESSLCONNECTERROR), which is the authority if the two ever differ.

## Where to go next

- [Everything decoded for curl](https://openbrokerapi.com/errors/curl)
- [Getting started with API trading](https://openbrokerapi.com/guides/getting-started-with-api-trading): What an API is, what you need and how to make a first call safely.
- [Brokers](https://openbrokerapi.com/brokers): The record for each broker: access, limits, endpoints and error codes.
- [Platform APIs](https://openbrokerapi.com/platforms): APIs that belong to trading software offered by many brokers.
- [Error codes](https://openbrokerapi.com/errors): What each error means, and the fix where the source gives one.

## Licence and how to cite

The records behind this page are all rights reserved. This file is the page itself, at its own address, in another format. It is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Quote from it with a link to the page.

Cite as: curl exit code: CURLE_SSL_CONNECT_ERROR (35). Broker API Hub, https://openbrokerapi.com/errors/curl/35, newest check 2026-10-09.

Where you rely on a single figure, cite the source and the checked date printed beside it as well. Where this page and a broker's own documentation differ, the documentation wins.