# Connect ingestion clients over a private network

Coordinator DB accepts ingestion through its native client or HTTP SQL interface. It does not provision a cloud private endpoint or a managed ingestion connector. A private ingestion setup therefore connects your own importer to a reachable listener using your network's routing and access controls.

## Establish the SQL path first

Choose the server address the importer can reach and confirm the listener is enabled. From the importer host, check HTTP readiness and a small authenticated request before sending data:

```sh
curl --silent http://db.internal:7401/ping
curl --silent --user "$COORDINATOR_USER:$COORDINATOR_PASSWORD" \
  --data-binary 'SELECT 1 FORMAT csv' http://db.internal:7401/
```

Use these plain HTTP examples only on a trusted route. The server does not provide TLS; external TLS termination or a protected tunnel belongs to your deployment.

## Validate ingestion separately

Create an explicit destination schema and upload a small file with a supported format. Check counts and values before increasing batch size. Keep network endpoint identifiers in the infrastructure configuration rather than inventing SQL settings for them. A successful health check confirms reachability, while an authenticated query also checks credentials.

See [HTTP interface](https://coordinatordb.com/docs/concepts/features/interfaces/http), [batch inserts](https://coordinatordb.com/docs/concepts/features/operations/insert/bulkinserts) and [listener settings](https://coordinatordb.com/docs/reference/settings/server-settings/settings/listen).