Settings & API Keys
Settings is organized into tabs. Here’s what each one does.
→ Open it: app.synaptyx.pro/dashboard/settings
| Tab | What you manage |
|---|---|
| Account | Email, password, display currency, and timezone (used everywhere dates appear). |
| Security | Enable two-factor authentication (2FA) and review sessions. |
| API Keys | Create and revoke syx_live_… keys for the REST API and MCP. |
| Telegram | Connect a Telegram bot (your own or the platform’s) and saved chats. |
| Notifications | Default notification channels and preferences. |
| Bot filtering | Your IP and user-agent blocklists used by the bot filter. |
API Keys
The API Keys tab is where you generate credentials for the REST API and MCP.
Two quick paths:
- MCP key — one click, auto-selects the
mcp:*scope (requires Pro/Scale). - Read-only key — pick which resources it can read; toggling a resource grants
its
read:(and where availablesearch:) scope.
A key is shown only once. When you create it, the full syx_live_… value appears
a single time — copy it immediately. There is no reveal endpoint (this mirrors
Stripe and GitHub). Lose it and you simply create a new one. Synaptyx stores only a
hash and a 12-character display prefix.
Each key shows its scopes, last-used time, and an audit feed. Revoking is a soft delete (the row is kept for audit). The full key lifecycle, scopes, and plan gating are documented in API → Authentication.
Security & 2FA
Enable two-factor authentication for an extra layer beyond your password. Your session is kept secure and can be revoked instantly — at the device, account, or whole-workspace level — so a lost or compromised login can be cut off immediately.
Bot-filtering blocklists
Add IP ranges (CIDR supported) and user-agent regex patterns to drop matching traffic before it’s recorded. These feed directly into the hard bot filter.