> Part of the walkerOS documentation. Project overview and full index: <https://www.walkeros.io/llms.txt>

# API Destination

Send walkerOS events to any HTTP(S) endpoint with customizable data transformation and flexible transport options.

<!-- -->

Where this fits

API is a **destination** in the walkerOS flow:

Sends events to any HTTP endpoint with customizable headers, data transformation, and multiple transport options.

## Environments[​](#environments "Direct link to Environments")

| Environment | Package                            | Use Case                       |
| ----------- | ---------------------------------- | ------------------------------ |
| **Web**     | `@walkeros/web-destination-api`    | Browser-side with fetch/beacon |
| **Server**  | `@walkeros/server-destination-api` | Node.js with native HTTP       |

## Features[​](#features "Direct link to Features")

* **Flexible URL Configuration** - Send events to any HTTP(S) endpoint
* **Custom Headers** - Add authentication tokens, API keys, or custom headers
* **Data Transformation** - Transform event data before sending
* **Multiple Transports** - Web: fetch, XHR, beacon; Server: native HTTP/HTTPS
* **Batching** - Set `config.batch` to send many events in one request

## Quick Start[​](#quick-start "Direct link to Quick Start")

Choose your environment:

* [Web (Browser)](https://www.walkeros.io/docs/destinations/api/web.md) - fetch, XHR, beacon transports
* [Server (Node.js)](https://www.walkeros.io/docs/destinations/api/server.md) - native HTTP/HTTPS

## Common Use Cases[​](#common-use-cases "Direct link to Common Use Cases")

* Sending events to custom analytics backends
* Integrating with internal APIs
* Forwarding events to webhooks
* Building custom data pipelines