Automate your on-call with the Polylane API.

Plug Polylane into your own alerting, dashboards and scripts: start investigations, pull issues and query your infrastructure, with scoped keys.

Start investigations from your own alerting and scripts.

Start an investigation from your own alerting, pull issues into your dashboards, or query the context graph from a script.

zsh
❯ curl https://api.polylane.com/v1/issues/search \
-H "Authorization: Bearer $POLYLANE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"workspaceId": "ws_YOUR_WORKSPACE_ID",
"prompt": "checkout timeouts"}'
[
{ "title": "Checkout p99 up 18x since 20:14",
"severity": "critical", "status": "confirmed" }
]

Give each script an API key with only the access it needs.

Scoped keys for every job, and you can revoke any of them at any time.

deploy-gate
Issues: read
2m ago
alert-bridge
Issues: read · Threads: write
1h ago
old-dashboard
Context graph: read
Active Revoked

Outcomes

Real numbers from Polylane customers.

Common questions.

Where are the docs?

In the API reference, generated from the OpenAPI spec at api.polylane.com/v1/doc.

How do I authenticate?

With an API key from Settings, API Keys, sent as a bearer token, or with OAuth for apps that act for a user.

What can I build with it?

Anything that needs production context: deploy gates, alert bridges, dashboards or your own internal tools.

Platform
Surfaces

Nobody should be on-call.