Routers Introduction
Routers
This group of endpoints allows you to manage routers within the Events & Actions system.
Routers represent actions that direct message data from Route Inputs to appropriate destinations or external systems. They are the output side of your event flow, determining where and how your PubNub events are delivered. In the Admin Portal UI, routers are referred to as "actions".
Supported Integrations:
- AWS Services: Kinesis Data Streams, SQS, S3
- Webhooks: Generic HTTP webhooks and IFTTT-specific webhooks
- Message Brokers: AMQP/RabbitMQ and Kafka
Key Features:
- Multiple destination types for flexible integration
- Configurable retry policies for reliable delivery
- Support for message batching to optimize throughput
- Multiple output formats (v1.0, v2.0, v2.1) for backward compatibility
- Full CRUD operations for complete lifecycle management
Router Configuration: Each router type has specific configuration requirements. For example, AWS integrations require credentials and resource identifiers, while webhooks need URLs and optional authentication headers.
GET routerGet
Get all information about a single router ([action](/docs/serverless/events-and-actions/overview#actions)).
PUT routerPut
Update information for a single router ([action](/docs/serverless/events-and-actions/overview#actions)).
DELETE routerDelete
Delete all information available for a single router ([action](/docs/serverless/events-and-actions/overview#actions)).
GET routersGetAll
Get information about all previously created routers ([actions](/docs/serverless/events-and-actions/overview#actions)).
POST routerPost
Create a single router ([action](/docs/serverless/events-and-actions/overview#actions)) passing messages (events) of a given type.