> For the complete documentation index, see [llms.txt](https://www.kauneonga.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.kauneonga.com/docs/release-notes/readme/may-1-2026-external-apis-and-webhooks-in-oncall-calendar.md).

# May 1, 2026 — External APIs and Webhooks in Oncall Calendar

Oncall Calendar now supports more flexible delivery methods for connected workflows. Teams can use external APIs and webhooks to route notifications and automate downstream actions with more control.

### What's new

#### Native integrations for Oncall Calendar

Oncall Calendar now supports native integration-based delivery methods.

This gives answering services a cleaner way to connect client workflows without relying on manual routing.

#### External API delivery methods

Teams can now use external APIs as a delivery method in Oncall Calendar.

This makes it easier to send schedule-based events and notifications into outside systems that support API-driven workflows.

#### Webhook support for connected workflows

Webhook-based delivery is also available for Oncall Calendar workflows.

This gives teams another lightweight option for triggering downstream systems, automations, and custom integrations.

### Key benefits

* Expand delivery options beyond standard notification methods
* Connect Oncall Calendar workflows to client-specific systems
* Support more consistent automation across schedules and escalations
* Reduce manual handoffs in connected workflows

### Why it matters

Answering services often need to deliver events into different client systems, not just one communication channel. Native integrations, external APIs, and webhooks give teams more flexibility to align Oncall Calendar with the tools each client already uses.

That improves consistency, reduces manual work, and makes connected workflow design easier to scale.

### Getting started

1. Review the delivery methods now available in Oncall Calendar.
2. Choose the method that best matches the client workflow.
3. Use native integrations where supported.
4. Use external APIs or webhooks when a client needs a custom connection.

{% hint style="info" %}
Choose the delivery method based on the system you need to reach and the level of control the workflow requires.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.kauneonga.com/docs/release-notes/readme/may-1-2026-external-apis-and-webhooks-in-oncall-calendar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.