How DSALTA integrates with Render — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to Render using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules. Compliance checks re-run once a day at 02:00 America/New_York.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Render account.
DSALTA reads the Render owners your API key can see — the account that authorised the connection and any workspaces it belongs to, with their names and emails, which appears on your Access page; and your Render resources, which appear on your Inventory page. Render’s API exposes no workspace member list, so there is no user roster to read, and every row is labelled an active owner.It calls these Render endpoints:
/owners
/services
/postgres
/redis
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Render environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the Render card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Render. This can happen if the API key was revoked or rotated in your Render Dashboard.
Data is not syncing
Confirm the connected API key is still active (it may have been revoked in Account Settings → API Keys) and that the key belongs to an account with admin access, then click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once.
Create a Render API key in your Render Dashboard and paste it below to connect your account.Before you begin
Render account with admin access
You will need:
Field
Where to find it
Example
Render API Key
Create a key at Render → Account Settings → API Keys. · Open
—
1
Start in DSALTA
Open Integrations in the DSALTA sidebar, find Render, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
2
Integrating Render with DSALTA means
DSALTA will only be able to read your Render resources to monitor and record statuses for security compliance. Only Render services reach your Inventory page — DSALTA also reads your Postgres and Redis instances on every sync, but does not list them as inventory items, and it never calls an environments endpoint.DSALTA monitors everything the API key can read. Configure scope on the integration’s Manage screen is read-only — it shows what DSALTA is permitted to read and has no Save action.
3
Create API Key in Render
Log in to your Render Dashboard. Navigate to Account Settings → API Keys. Click Create API Key. Enter a name (e.g. DSALTA) and click Create. Copy the key immediately (it is shown only once).You can go straight to the key list at dashboard.render.com/u/settings — the API Keys section is on that page.
A Render API key is not scoped to a single workspace — Render grants it access to every workspace the account belongs to. If the person creating the key is a member of more than one workspace, expect resources from all of them to appear.
Render publishes a direct link that opens the create-key dialog for you: https://dashboard.render.com/u/settings?add-api-key. The API Keys section lives on the same Account settings page, in the right-hand nav under API Keys.
Render’s own resource records tell you which workspace each item belongs to (owner_id), and that is what lands in the Account column on your Inventory page — so if the key spans several workspaces you can tell the services apart there.
4
Enter API Key
Paste your Render API Key below and click Connect.API Key — Example: rnd_xxxxxxxxxxxx
DSALTA validates the credential when you click Connect. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.
If the connection is rejected. Invalid API key or insufficient permissions.The on-screen message is generic — see Connection error messages.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)
