Connection Strings: HTTP/S

Choose None when the HTTP/S service does not require credentials. Enter the base service URI only. This URI is still used as the base URL for later HTTP calls.

Choose API Key when the service expects a named key and secret. Provide the parameter name and the secret value. By default, DataZen sends the API key as an HTTP header. Select Send as Query String... only when the service requires the key as a query parameter.

If the secret must be Base64-encoded before it is sent, enable Encode Secret... / Use Base64 Encoding. See Base64 Encoding for how this option interacts with authentication schemes.

Example: ActiveCampaign

• URI: https://COMPANYNAME.api-us1.com/api/3
• Authentication: API Key
• Parameter: Api-Token
• API Key: secret provided by ActiveCampaign

Choose Basic when the service expects a user ID and password. DataZen sends credentials using the standard Authorization HTTP header for Basic authentication.

Enable Encode Secret... / Use Base64 Encoding when the password (or secret) must be Base64-encoded before the Basic Auth header is built. Basic authentication then applies its own credential encoding as required by the HTTP scheme. See Base64 Encoding.

Example: Twilio

• URI: https://api.twilio.com
• Authentication: Basic
• User Id: your Twilio Account SID
• Password: secret provided by Twilio
• Base64 Encoding: Yes

Choose Token when the service expects a token value sent with the Authorization HTTP header using the Token authentication scheme. Provide the token value. Optionally enable Base64 encoding of the secret first when the service requires it.

Token and Bearer are different authentication schemes. Use Token when the service documents Token auth; use Bearer when it expects a Bearer token or OAuth access token.

Choose Bearer when the service expects a Bearer token in the Authorization header. You can paste a long-lived token directly, or use the OAuth wizard to obtain access tokens (and refresh tokens when the HTTP API supports them).

The OAuth wizard is available in both the Web Portal and DataZen Manager. Use Obtain OAuth Token... to configure client-flow authorization and issue tokens for the service.

Common Bearer token approaches:

• Authorization Code — authenticate in a browser, approve access, then exchange the authorization code for tokens.
• Client Credentials — obtain tokens using application credentials without an interactive user login when the service supports this machine-to-machine flow.
• Service-issued Bearer tokens — some providers issue long-lived Bearer tokens that you copy into the Bearer Token field. These tokens can still expire, rotate, or be revoked; update the connection when the provider issues a replacement.

Choose Session/Custom when the service requires a preliminary call to a session or token endpoint, then uses the returned value on later requests. A common pattern is exchanging a signed assertion for an access token.

Session Endpoint

Enter the session endpoint URI and any payload required for POST/PUT calls. When JWT is used on a self-hosted agent, the payload can include the {jwt} replacement token. For example, Google Analytics uses:

grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion={jwt}

Security Token Response

If the session endpoint returns a security token, enable Endpoint returns a security token. Set the Response Node to the JSON or XML path where the token appears, then choose whether to send it as a Bearer Token header or as a named Query Parameter.

JWT Payload Setup (Self-Hosted)

On self-hosted agents, click Build JWT Token... to configure the signed JWT assertion required by the session endpoint, including claims and the private key. The example below shows Google Analytics GA4 settings with custom claims.