AlertOps SDKs for Python, TypeScript, Go, Java and .NET
The AlertOps SDKs let you automate on-call setup, alert ingestion, escalation and status pages from Python, TypeScript, Go, Java or .NET with one install and an API key.
Overview
Relevant for Engineering teams automating AlertOps from their own code
The AlertOps SDKs are official client libraries for the AlertOps API. They give your scripts, services and CI pipelines the same capabilities as the AlertOps app: create users and groups, build on-call rotations, define escalation policies, send alerts in from any system, manage alerts, and publish status pages. All five SDKs cover the full API with the same structure and names, so teams that work in different languages share one way of automating AlertOps.
Key benefits:
- Complete API coverage — every AlertOps endpoint is available as a method, such as groups.list or escalation_policies.create.
- On-call as code — keep groups, rotations, escalation policies and integrations in version control and apply them repeatably.
- Built-in best practices — helpers create shifts and escalation ladders that follow AlertOps scheduling rules.
- The semantic layer — describe on-call intent ("after-hours rotation, escalate to the manager after 15 minutes") and the SDK plans, applies and verifies the configuration for you.
- Consistent across languages — the same operations, helpers and errors in every SDK.
Choose your SDK
Relevant for Developers picking the library for their stack
| Language | Package | Install |
| Python 3.10+ | alertops-sdk on PyPI | pip install alertops-sdk |
| TypeScript and JavaScript (Node 18+) | @alertops/sdk on npm | npm install @alertops/sdk |
| Go 1.23+ | github.com/alertops/alertops-go | go get github.com/alertops/alertops-go |
| Java 17+ | com.alertops:alertops-sdk on Maven Central | Add the dependency to your pom.xml or Gradle build |
| .NET 8 | AlertOps.Sdk on NuGet | dotnet add package AlertOps.Sdk |
Each SDK reads your AlertOps API key from the ALERTOPS_API_KEY environment variable, a .env file or a client option, and is ready to call the API in two lines.
What you can automate
Relevant for Teams planning what to automate first
| Area | Examples |
| People and on-call | Create users, build groups, add members and create rotating or fixed shifts |
| Escalation | Create escalation policies with Primary, Secondary and Manager roles, or response plays with timed steps |
| Alert sources | Create inbound API integrations, send alerts from your tools and monitor heartbeats |
| Alerts | List, assign, close and report on alerts; act on notification links from bots and chat tools |
| Automation | Build workflows, connect outbound integrations and schedule maintenance windows |
| Status pages | Build status pages and post incidents and scheduled maintenance |
| Administration | Manage alert types, roles, topics and analytics reports |
Learn more
Relevant for Developers getting started
Start with the Getting Started article for your language, then follow the guides for each area. The guides apply to every SDK and show code in all five languages where it helps.
Full developer documentation, including a reference of every method, ships with each library and lives in its GitHub repository: github.com/alertops/alertops-python, alertops-node, alertops-go, alertops-java and alertops-dotnet.
Related Articles
- Getting Started with the AlertOps Python SDK
- Getting Started with the AlertOps TypeScript SDK
- Getting Started with the AlertOps Go SDK
- Getting Started with the AlertOps Java SDK
- Getting Started with the AlertOps .NET SDK
- Planning On-Call Setups with the AlertOps Semantic Layer
Need help?
Email support@alertops.com or contact your AlertOps representative.