Render
Collect service and workspace-owner inventory as read-only deploy/hosting compliance evidence through the Render REST API v1. Render's public API does not document a team-member/role-listing endpoint as of this writing, so member-role access-review evidence is NOT covered here -- track it manually until Render documents one, or reclassify to a bespoke connector if that changes.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Service inventory (read-only)
- Workspace/owner inventory
- Member-role evidence NOT covered (no documented endpoint) -- track manually
Endpoints this template queries
The exact Render API endpoints called once connected. All read-only GET requests unless noted.
- GET/services
- GET/owners
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://api.render.com/v1)
- Endpoints (JSON)(prefilled: [ { "id": "services", "name": "Services", "path": "/services" }, { "id": "owners", "name": "Workspace owners", "path": "/owners" } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Render evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Render evidence
Get a guided demo, or start by scanning any domain for free.