Delivery destinations overview

A delivery destination is where Mapping.Travel sends a completed mapping job. You can configure any combination of three types:

Type	Best for	Trigger	Payload
Webhook	Real-time integrations	HTTP POST per event	HMAC-signed JSON
Amazon S3	Batch ingestion, durable storage	Per completed job	Result file (CSV/JSON/XLSX)
SFTP	Partner integrations, legacy systems	Per completed job	Result file (CSV/JSON/XLSX)

All destinations share one delivery queue with bounded retries (1m → 5m → 30m → DEAD) and auto-disable on 5 dead attempts within 24 hours.

Getting started

Receive real-time HMAC-signed JSON payloads on your HTTPS endpoint.

Push result files directly to an S3 bucket or S3-compatible target.

Deliver result files to any SFTP server using password or SSH-key auth.

File name pattern, supported formats (CSV/JSON/XLSX), and column reference.

Retry schedule, failure classes, dead-lettering, and auto-disable logic.

HMAC-SHA256 verification in Node, Python, Kotlin, and Go.

Trigger a test delivery and interpret the result for each destination type.