This is an application which is using gosoline and TLS-Client to run a simple request forwarding service with the option to use specific tls fingerprints which are implemented in TLS-client

  • By CaptainBarnius
  • Last update: Dec 29, 2022
  • Comments: 0



This is an application which is using gosoline and TLS-Client to run a simple request forwarding service with the option to use specific tls fingerprints which are implemented in TLS-client.

Supported Clients

  • chrome_105
  • chrome_104
  • chrome_103
  • safari_15_6_1
  • safari_16_0
  • safari_ipad_15_6
  • safari_ios_15_5
  • safari_ios_15_6
  • safari_ios_16_0
  • firefox_102
  • firefox_104
  • firefox_105
  • opera_89
  • opera_90
  • opera_91
  • zalando_android_mobile
  • nike_ios_mobile
  • nike_android_mobile

Need other clients?

Please open an issue on this github repository. In the best case you provide the response of requested by the client you want to be implemented.


You can just run the prebuilt binaries in dist. There is a binary for linux, macos and windows. Just modify your config file next to the binary as explained below and start the application.

Build API from source

When you want to build the application from source, make sure to also checkout this repository on the branch tls-client-api next to this project. Afterwards you can just run the following script: cmd/tls-client-api/ SOME_BUILD_IDENTIFIER and it should build the binaries for you

Configuration & Start

  • Configure stuff like api port and authentication keys in the cmd/tls-client-api/config.dist.yml file.
  • You can also configure if the api should automatically follow redirects (3XX Status Codes) or not. Per Default the API does not follow redirects.
  • The endpoint is
  • You need to set a x-api-key header with an auth key from the config file. This is for protecting the API when you host it on some server. Requests without the correct keys in the header will be rejected.


  • Applications powered with gosoline automatically host a health check endpoint which is by default on port 8090 under the path /health. So in our case it would be
  • Applications powered with gosoline automatically host a metadata server for your application to provide insights into your application. The metadata server is hosted on port 8070 and has three endpoints. /, /config, /memory this should help you debugging your application. Do not make this endpoints public available when you host the Application on some server in the internet. You would make your config file public available.

How to use this api when it is running

You need to do a POST Request against this running API Service with the following JSON Request Body:

  "sessionId": "reusableSessionId",
  "tlsClientIdentifier": "chrome_103",
  "followRedirects": false,
  "insecureSkipVerify": false,
  "isByteResponse": false,
  "timeoutSeconds": 30,
  "customTlsClient": {
    "ja3String": "771,4865-4866-4867-49195-49199-49196-49200-52393-52392-49171-49172-156-157-47-53,0-23-65281-10-11-35-16-5-13-18-51-45-43-27-17513,29-23-24,0",
    "h2Settings": {
      1: 65536,
      3: 1000,
      4: 6291456,
      6: 262144
    "h2SettingsOrder": [
    "pseudoHeaderOrder": [
    "connectionFlow": 15663105,
    "priorityFrames": [

  "proxyUrl": "",
  "headerOrder": [
  "headers": {
    "key1": "value1",
    "key2": "value2"
  "requestCookies": [
      "name": "cookieName",
      "value": "cookieValue",
      "path": "cookiePath",
      "domain": "cookieDomain",
      "expires": "cookieExpires"
  "requestUrl": "",
  "requestBody": "", // needs to be a string!
  "requestMethod": "GET"
  • If tlsClientIdentifier is not specified chrome_105 will be used.
  • You can use your own client by providing customTlsClient instead of tlsClientIdentifier
  • sessionId is optional. When not provided the API creates a new Session. On every forwarded request you will receive the sessionId in the response to be able to reuse sessions (cookies).
  • Be aware that insecureSkipVerify and the timeoutSeconds can not be changed during a session.
  • followRedirects and proxyUrl can be changed within a session.
  • If you do not want to set requestBody or proxyUrl use null instead of empty string
  • When you set isByteResponse to true the response body will be a base64 encoded string. Useful when you want to download images for example.
  • Header order might be random when no order is specified

h2 seetings IDs

	SettingHeaderTableSize      0x1
	SettingEnablePush           0x2
	SettingMaxConcurrentStreams 0x3
	SettingInitialWindowSize    0x4
	SettingMaxFrameSize         0x5
	SettingMaxHeaderListSize    0x6


The Response from the API looks like that:

  "sessionId": "some reusable sessionId",
  "status": 200,
  "body": "The Response as string here or the error message",
  "headers": {},
  "cookies": {}
  • In case of an error the status code will be 0

JavaScript Fetch minified example

var myHeaders = new Headers();
myHeaders.append("x-api-key", "my-auth-key-1");
myHeaders.append("Content-Type", "application/json");

var raw = JSON.stringify({
  "tlsClientIdentifier": "chrome_105",
  "requestUrl": "",
  "requestMethod": "GET"

var requestOptions = {
  method: 'POST',
  headers: myHeaders,
  body: raw,
  redirect: 'follow'

fetch("", requestOptions)
  .then(response => response.text())
  .then(result => console.log(result))
  .catch(error => console.log('error', error));

Python Requests minified example

import requests
import json

url = ""

payload = json.dumps({
  "tlsClientIdentifier": "chrome_105",
  "requestUrl": "",
  "requestMethod": "GET"
headers = {
  'x-api-key': 'my-auth-key-1',
  'Content-Type': 'application/json'

response = requests.request("POST", url, headers=headers, data=payload)


CURL minified example

curl --location --request POST '' \
--header 'x-api-key: my-auth-key-1' \
--header 'Content-Type: application/json' \
--data-raw '{
    "tlsClientIdentifier": "chrome_105",
    "requestUrl": "",
    "requestMethod": "GET"

Frequently Asked Questions / Errors

  • I can not do a successful POST Request.

Be aware that when you do a POST Request and want to provide a forwarded request body in the requestBody field it has to be a string. That means if you want to send JSON you need to stringify this JSON to a string first.

  • **How can I use other request body content types besides json? **

requestBody accepts strings and forwards them as the payload. combined with the content-type header the api makes the actual request body out of it. You can use for example application/x-www-form-urlencoded content type in the header and then just provide as request body a string similar to key=value&key=value

For more Questions and answers please refer to


Join my discord support server: https: // / 7Ej9eJvHqk No Support in DMs!