Get logs (runtime, build, static) out of Vercel programmatically by configuring a Drain via the REST API

Documented steps

1. Confirm plan eligibility: Drains require Pro or Enterprise (Hobby/Pro Trial must upgrade); Audit Log Drains require Enterprise specifically.
2. Authenticate with 'Authorization: Bearer $VERCEL_TOKEN' and add teamId=<id> or slug=<slug> as a query param on every Drains call since drains are team-scoped resources.
3. Optionally validate your endpoint first: use the drain-delivery-validation endpoint, passing the same schemas and delivery config you intend to create, to confirm your receiving endpoint responds correctly before going live.
4. Create the drain: POST /v1/drains?teamId=... with body { name, projects: 'all'|'some', projectIds: [...] (if 'some'), schemas: { log: { version: 'v1' } }, delivery: { type: 'http', endpoint: 'https://your-endpoint', encoding: 'json'|'ndjson', compression: 'gzip'|'none', headers: {...}, secret: '<optional-signing-secret>' } } — use schemas.log for runtime/build/static logs (other schema names: trace, analytics, speed_insights, audit_log).
5. Optionally add sampling: [{ type: 'log', rate: 0.1, env: 'production', requestPath: '/api' }] to control volume/cost, and select log sources (static/lambda/edge/build/external/firewall/redirect) and environments (production/preview) in the dashboard's Additional configuration for logs (not all fields are exposed identically via API vs UI).
6. Vercel POSTs batched JSON or NDJSON log objects to your endpoint over HTTPS; each entry includes id, deploymentId, source (build|edge|lambda|static|external|firewall|redirect), host, timestamp, projectId, level, message, plus optional buildId, requestId, statusCode, traceId/spanId, and a nested proxy object — verify the x-vercel-signature header against your configured secret to authenticate deliveries.
7. List/manage drains: GET /v1/drains?teamId=... to list, DELETE /v1/drains/{id}?teamId=... to remove — respect drain-specific rate limits (creation ~30/min, retrieval ~100/min, deletion ~30/min per user).
8. For ad hoc/interactive log viewing instead of a pull-based API, use the dashboard's Logs tab — Vercel does not expose a general-purpose 'pull logs' REST endpoint outside Drains; runtime log retention is only 1 hour (Hobby), 1 day (Pro), 3 days (Enterprise), or 30 days with Observability Plus, so Drains are the only way to persist logs long-term.
9. Official docs verified: https://vercel.com/docs/drains/using-drains | https://vercel.com/docs/drains/reference/logs | https://vercel.com/docs/rest-api/drains/create-a-new-drain | https://vercel.com/docs/logs/runtime | Reference: https://vercel.com/docs/drains