ReferenceDriverHTTPConnect Server

Connect an HTTP Server

Connect to an HTTP server using Synnax.

Prerequisites

Before you can connect to an HTTP server, you will need to ensure that you have the following:

  1. A Synnax Core running on your network.
  2. A Synnax Driver running on your network. This Driver must be connected to the Core and able to reach your HTTP server.
  3. The Synnax Console installed on your local machine.
  4. An HTTP server running on your network that is reachable by the Driver.

Configuration Parameters Reference

ParameterTypeRequiredDefaultDescription
namestringYes-Human-readable server name for identification in Console
rackstringYes-Synnax Driver (rack) key that will connect to the HTTP server
hoststringYes-Host and port of the HTTP server (e.g., 192.168.1.100:8080 or localhost:443)
securebooleanNotrueUse HTTPS (true) or HTTP (false)
timeout_msintegerNo100Request timeout in milliseconds
verify_sslbooleanNotrueWhether to verify SSL/TLS certificates
authobjectNononeThe configuration used to authenticate with the HTTP server
health_checkobjectYes-The configuration the Driver uses to track the health of the HTTP server

Setting verify_ssl to false should be used when the HTTP server does not have a verified SSL certificate, which is common for internal servers not connected to the public internet.

Authentication Reference

The HTTP driver supports four authentication methods. Authentication is configured at the device level and applied to every request.

None (Default)

No authentication headers are added to requests.

{ "type": "none" }

Bearer Token

Adds an Authorization: Bearer <token> header to every request.

ParameterTypeRequiredDescription
tokenstringYesThe bearer token value
{ "type": "bearer", "token": "my-secret-token" }

Basic (Username and Password)

Adds an Authorization: Basic <credentials> header using Base64 encoded username:password.

ParameterTypeRequiredDescription
usernamestringYesUsername
passwordstringYesPassword
{ "type": "basic", "username": "admin", "password": "secret" }

API Key

Sends an API key as either a custom header or a query parameter.

ParameterTypeRequiredDefaultDescription
keystringYes-The API key value
send_asstringYes-How to send the key: "header" or "query_param"
headerstringNo-Header name (required when send_as is "header")
parameterstringNo-Query parameter name (required when send_as is "query_param")
{ "type": "api_key", "send_as": "header", "header": "X-API-Key", "key": "abc123" }
{ "type": "api_key", "send_as": "query_param", "parameter": "api_key", "key": "abc123" }

Health Check Configuration

The driver periodically checks whether the HTTP server is reachable. We recommend choosing a path that sends a very small response body if the server does not have a dedicated /health, /status, or /ping endpoint.

Health Check Parameters

ParameterTypeRequiredDefaultDescription
methodstringYes-HTTP method for the health check ("GET" or "POST")
pathstringNo"/health"URL path to request
headersobjectNo-Additional headers to include
query_paramsobjectNo-Query parameters to include
bodystringNo-Request body (POST only)
responseobjectNo-Optional response validation configuration

Response Validation Parameters

When a response object is provided, the driver validates the response body against an expected value:

ParameterTypeRequiredDescription
pointerstringYesJSON Pointer into the response body (e.g., /status)
expected_value_typestringYesType of the expected value: string, number, boolean, null
expected_valueJSONYesThe expected value at that pointer

How-To

Console

Python