---
Title: Deliver destinations
URL Source: https://company-skill.com/p/eb/eb-deliver-destinations
Language: en
Description: You want to route EventBridge events to external systems such as HTTP APIs, Alibaba Cloud OSS buckets, or MQTT brokers, and ensure secure, reliable delivery with proper authentication and error…
---

# Deliver destinations

Part of **EventBridge**. Route queries via `POST https://company-skill.com/api/route`.

## What You Want to Do

You want to route EventBridge events to external systems such as HTTP APIs, Alibaba Cloud OSS buckets, or MQTT brokers, and ensure secure, reliable delivery with proper authentication and error handling.

**Typical User Questions**:
- HTTP API
- How to deliver events to OSS?
- Can I push events to an MQTT broker?

- Is there a way to manage API destinations in console?

## Decision Tree

Pick the best path for your situation:

- **If** you need to configure **API Destination** with **Bearer Token** or AccessKey authentication programmatically → Use API (go to *eb/eb-event-delivery*)
- **If** you want to quickly **Publish Event** and validate delivery via MNS using a graphical interface → Use (go to *eb/eb-event-delivery*)
- **If** you are setting up a **Message Outflow Task** to OSS/MQTT and require **Retry Policy** or **Event Pattern** filtering without code → Use (go to *eb/eb-event-delivery*)
- **Otherwise (default)** → Start with **** if you're testing or lack automation needs; use the API path only if you require scripting, CI/CD integration, or bulk management of **API Destinations**.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| API | medium | Yes | Yes | Supports **Bearer Token** and AccessKey auth; PutEvents max 100 events/request | `eb/api/eb-event-delivery` |
| Console / Dashboard | low | No | No | **Publish Event** UI allows instant testing; **Send/receive msgs** via MNS for validation | `eb/guide/eb-event-delivery` |

## Path Details

### Path 1: API 

**Brief Description**: EventBridge Event Delivery API HTTP **API Destination** MQTT/OSS/RabbitMQ **Sink** PutEvents Key operations include **Create API Destination**, **Deliver Events to OSS**, and **Verify Event Signature**.

**Key technical facts**:
- Billing: API 
- Auth method: Bearer Token Authorization: Bearer <your_api_key> AccessKey accessKeyId accessKeySecret
- Regions available: cn-hangzhou, cn-shanghai, cn-beijing

**When to Use**:
- **API Destinations**

### Path 2: Console / Dashboard
**Brief Description**: EventBridge **Publish Event**, **Message Outflow Task**, **API Destinations**, MNS **Send/receive msgs** Users configure **Connection Configuration** panels and define **Event Pattern** filters visually.

**Key technical facts**:
- Billing: **API Destination** MNS 
- Auth method: SSO

**When to Use**:
- **Event Pattern**

**When NOT to Use**:
- **API Destinations**

**Known Limitations**:
- **API Destination** 8KB
- **Message Outflow Task** 
- **API Destinations** **Connection Configuration** 
- MNS “Receive message”

## FAQ

Q: Which path should I start with?
A: Start with **** if you're prototyping, testing event formats, or lack coding resources. Switch to the API path only when you need automation, bulk operations, or custom auth logic.

Q: What if I need to deliver large payloads (>8KB) to an HTTP endpoint but used the console path?
A: You'll hit the **8KB request size limit** for **API Destination** calls in the console, causing delivery failures. Use the API path (max 256 KB per request) instead.

Q: What if I want to automate daily event routing to OSS but chose the console path?
A: You’ll be unable to schedule or script the **Message Outflow Task** because the console doesn’t support automation — you’ll have to manually trigger it every time.

Q: Can I use OAuth authentication with the API path?
A: The API path supports **Bearer Token** and AccessKey; for OAuth, you must handle token acquisition externally and pass it as a **Bearer Token**. The console’s **Connection Configuration** panel natively supports **OAuth** as an option.

Q: Does the console support **Retry Policy** configuration?
A: Yes — when creating a **Message Outflow Task** or **API Destination** in the console, you can configure retry attempts and backoff in the **Connection Configuration** settings.

Q: Are **Detail Type** filters usable in both paths?
A: Yes — **Event Pattern** rules (which include **Detail Type**) can be defined in both the console UI and via API when creating rules that route to external **Sink** targets.

## Related queries

deliver events to external API, send events to OSS, push events to MQTT broker, configure API destination, verify event delivery, manage API destinations in console, event delivery to external endpoint, how to send EventBridge events externally, can I deliver to MQTT, test event delivery, publish ev

---
Part of [EventBridge](https://company-skill.com/p/eb.md) · https://company-skill.com/llms.txt