Skip to main content
Use this destination when the system you need to feed has no native connector but does have an HTTP API. The REST endpoint destination POSTs data to an HTTP endpoint. It supports synchronous and asynchronous modes, bearer token authentication, and configurable timeouts.

Request

The pipeline sends an HTTP POST request with the following JSON payload:

Expected Response

The endpoint must return a JSON response with the following structure:
The response data is forwarded to downstream steps in the pipeline.

Batching

By default (batchSize = 0) the pipeline makes exactly one call carrying every row. Set batchSize to a positive number to send row-based (CSV) payloads in batches of that many rows, one call per batch, in source order. Each batched request carries the same envelope plus two extra top-level fields:
Batched requests are only checked for an {"error": ...} response; the response data is not forwarded anywhere. JSON and XML payloads (rawData) are always sent in a single call regardless of batchSize. With async set, each batch waits for its own callback before the next batch is sent.

Sync and Async Modes

Set async to control whether the pipeline waits for a response:

Authentication

Set bearerToken to include an Authorization: Bearer {token} header on every request. If omitted, requests are sent without authentication.

Timeout

The timeoutMs field controls the maximum time in milliseconds the pipeline will wait — for the HTTP response when async is false, or for the callback when async is true. The default is 300000 ms (5 minutes).

Configuration Example

Field Reference

Completion Notification

A pipeline notification is published to ActiveMQ on completion. See Notifications for details.