> For the complete documentation index, see [llms.txt](https://answeringservicecare.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://answeringservicecare.com/docs/useful-resources/integrations/external-api-dispatching.md).

# External API Dispatching

Use External API delivery in Oncall workflows to hand off message events to external systems.

## External API dispatching

External API dispatching lets ASC hand off on-call delivery events to another system.

Use it when a client needs message delivery to trigger an external application instead of, or alongside, standard call, SMS, email, or fax delivery.

### Where it appears

External API dispatching is used as a delivery method inside **Oncall Calendar**.

Admins add it to a contact or event when a workflow should send data to an external endpoint.

### Best fit

Use External API dispatching when you need to:

* send delivery events to a client system
* trigger account-specific workflows outside ASC
* replace manual relay steps with a system handoff

### Before you start

Confirm these basics first:

* the destination endpoint is available
* authentication requirements are known
* the receiving system can process the expected request
* fallback handling is defined if delivery fails

### Rollout guidance

1. define the business event that should trigger the handoff
2. confirm the endpoint and authentication requirements
3. configure the External API delivery method in the Oncall workflow
4. test with a real escalation path
5. validate failure handling and retries

{% hint style="warning" %}
Always test External API delivery with the real destination before rollout. A saved configuration does not confirm a working handoff.
{% endhint %}

### Related pages

* Oncall calendar
* Integrations


---

# 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://answeringservicecare.com/docs/useful-resources/integrations/external-api-dispatching.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.