Solution skill
Fivetran REST API uses Basic auth with base64 of API key and secret
Complete solution
Build the Authorization header as Basic base64(API_KEY value API_SECRET) for every Fivetran REST call; there is no bearer-token alternative on the management API.
Fivetran REST API uses Basic auth with base64 of API key and secret
TL;DR
Build the Authorization header as Basic base64(APIKEY value APISECRET) for every Fivetran REST call; there is no bearer-token alternative on the management API. Keep the key and secret in a secret manager and inject them at runtime; rotate on demand from the Fivetran dashboard and update the stored secret, not your code. If a call returns 401, check the key-secret pair and its rotation state before assuming the endpoint is wrong.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Context: Fivetran Connector SDK tooling docs (official fivetran/connectorsdktools repo): documents that the REST API authenticates with HTTP Basic where the base64 value encodes {apikey}:{apisecret} using the Fivetran API key and secret. The api_secret is a real credential: treat it like a password, store it in a secret manager, and never print it in build logs or commit it. Fivetran rotates keys on demand, so automation should read the key and secret from the environment or secret store at runtime rather than hardcoding them.
Evidence
Source: Fivetran Connector SDK tooling docs (official fivetran/connectorsdktools repo): documents that the REST API authenticates with HTTP Basic where the base64 value encodes {apikey}:{apisecret} using the Fivetran API key and secret. The api_secret is a real credential: treat it like a password, store it in a secret manager, and never print it in build logs or commit it. Fivetran rotates keys on demand, so automation should read the key and secret from the environment or secret store at runtime rather than hardcoding them.
Verified resolution: Build the Authorization header as Basic base64(APIKEY value APISECRET) for every Fivetran REST call; there is no bearer-token alternative on the management API. Keep the key and secret in a secret manager and inject them at runtime; rotate on demand from the Fivetran dashboard and update the stored secret, not your code. If a call returns 401, check the key-secret pair and its rotation state before assuming the endpoint is wrong.
Source URL: https://github.com/fivetran/connectorsdktools/blob/HEAD/codex/workflows/fixer.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_9bGIMsMBSVYN8uEC3HbpiQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Fivetran REST API uses Basic auth with base64 of API key and secret <span>— Vectle</span></a>