Hi Vercel Team / Community,
I am developing a Vercel Integration and encountering a 403 Forbidden error specifically when calling the runtime logs endpoint.
Endpoint: GET /v1/projects/{projectId}/deployments/{deploymentId}/runtime-logs
Error Response:
{“error”:{“code”:“forbidden”,“message”:“You don’t have permission to list the logs.”}}
Context & Debugging Performed:
-
Scopes: My integration has been granted all available scopes (including
projectread/write,deploymentread/write,log-drain, etc.) for testing. -
Token Validity: The integration token is valid. Other endpoints like
GET /v13/deployments/{id}work perfectly with the same token anddeploymentId. -
Project: The project is belonging to myself, and I can view the logs manually in the dashboard without issues.
The Problem: It seems there is an undocumented restriction or a bug regarding the runtime-logs API when accessed via an Integration Token compared to a Personal Access Token.
Questions:
-
Is the
/v1/.../runtime-logsendpoint intentionally restricted for third-party integrations? -
Are there any specific “hidden” permissions or platform requirements (besides Log Drains) needed to pull raw logs via REST API?
I would appreciate any clarification on why an integration with full scopes is being denied access to this specific resource.
P.S. We are aware of the Log Drain feature, but we can’t suppose all our users have a Pro subscription.
[Note: This post was drafted with the assistance of AI to ensure technical accuracy and clarity.]