Bright Data Snapshot Delivery Receiver

Overview

Treat snapshot delivery as an untrusted, repeatable data-transfer event. Configure delivery with the current POST /datasets/v3/deliver/SNAPSHOT_ID API, authenticate the managed destination, stream the body, validate it, and make downstream processing idempotent.

Prerequisites

• A completed approved snapshot and its expected schema
• A managed HTTPS endpoint with destination authentication
• Durable quarantine storage and a replay ledger

Instructions

Step 1: Establish the delivery contract

Read the receiver and Grep for body buffering, unauthenticated routes, hard-coded provider IPs, guessed retry schedules, and direct writes to trusted tables. Record the expected schema, format, destination, and ownership.

Step 2: Configure an approved destination