You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/getting-started.md
+44Lines changed: 44 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,50 @@ Add a warehouse connection to `.altimate-code/connections.json`. Here's a quick
81
81
82
82
For all warehouse types (Snowflake, BigQuery, Databricks, PostgreSQL, Redshift, DuckDB, MySQL, SQL Server) and advanced options (key-pair auth, ADC, SSH tunneling), see the [Warehouses reference](configure/warehouses.md).
83
83
84
+
### Connecting to Altimate
85
+
86
+
If you have an Altimate platform account, run `/connect` in the TUI, select **Altimate**, and enter your credentials in this format:
87
+
88
+
```text
89
+
instance-url::instance-name::api-key
90
+
```
91
+
92
+
For example: `https://api.getaltimate.com::acme::your-api-key`
93
+
94
+
-**Instance URL** — `https://api.myaltimate.com` or `https://api.getaltimate.com` depending on your dashboard domain
95
+
-**Instance Name** — the subdomain from your Altimate dashboard URL (e.g. `acme` from `https://acme.app.myaltimate.com`)
96
+
-**API Key** — go to **Settings > API Keys** in your Altimate dashboard and click **Copy**
97
+
98
+
Credentials are validated against the Altimate API before being saved. If you prefer to configure credentials directly (e.g. for CI or environment variable substitution), you can also create `~/.altimate/altimate.json` manually — if that file exists it takes priority over the TUI-entered credentials.
0 commit comments