Authentication
SDK, CLI, and Batch API requests go through your Sutro deployment. Use the same origin where you build your Functions, such ashttps://your-customer.app.sutro.sh, or your organization’s custom domain.
Manage deployment API keys
Open your Sutro deployment and select API Keys in the top bar. Anyone with access to the UI, including through SSM, can view the deployment’s key list, create keys, and revoke keys, including keys created by another user. No additional application sign-in is required. API requests still require a valid deployment API key. Create a named key and copy its setup commands. The full key is shown only once; the key list shows a masked preview. To replace a key, create a new one, update your clients, and revoke the old key from the same panel. Configure the deployment origin and key together:/v1 remain
supported. Raw HTTP examples append /v1 explicitly. Use HTTPS for hosted
deployments.
There is no shared default API URL. Keys work only with the deployment that
issued or imported them. Revoke and replace a key from the same API Keys
panel.
Verify your connection
Check that your deployment can authenticate the key and reach Batch before submitting a job:{"authenticated": true}. This check does not create
a job. See Check API access if it fails.
Save SDK credentials
To store both values in~/.sutro/config.json instead:
- Explicit
Sutro(api_url=..., api_key=...)values or setters SUTRO_API_URLandSUTRO_API_KEY- Values saved by
sutro login