Render · AsyncAPI Specification
Render Logs Subscription API
Version 1.0
Render exposes a documented public WebSocket surface for real-time log streaming. A client opens a WebSocket connection to wss://api.render.com/v1/logs/subscribe with an API key Bearer token and query filters (ownerId and one or more resource IDs, plus optional level, text, host, statusCode, method, task, type, and path filters). The server performs the HTTP-to-WebSocket upgrade (HTTP 101) and then pushes log messages to the client in real time as they are generated. All subscribed resources must be in the same region and belong to the same owner. This AsyncAPI document models that server-push WebSocket stream. Historical log retrieval is a separate REST endpoint (GET /logs), modeled in the OpenAPI document.
View Spec
View on GitHub
Cloud HostingPaaSDeploymentWeb ServicesDatabasesDevOpsAsyncAPIWebhooksEvents
Channels
/logs/subscribe
Receive real-time log messages pushed by Render over the WebSocket.
Real-time log subscription. After the WebSocket upgrade, the server sends log messages matching the subscription filters as they are generated.
Messages
LogMessage
Log Message
A single log line streamed in real time as it is generated.
Servers
wss
production
api.render.com/v1
Render Public API WebSocket log subscription endpoint. Full path wss://api.render.com/v1/logs/subscribe. Authenticated with an API key Bearer token.