Cable’s SFTP integration allows you to deliver data files directly to a dedicated, secure SFTP server. Once uploaded, Cable automatically processes your files and loads the data into your dedicated dataset for assurance checks.
This guide walks you through connecting to Cable’s SFTP server, configuring SSH key authentication, preparing your data files, and optionally encrypting them with PGP.
This guide assumes your Cable onboarding is complete and you have received your SFTP connection details from your Cable point of contact. If you haven’t started onboarding, reach out to your Cable contact to get started.
You upload CSV data files to Cable’s SFTP server using SSH key authentication. Cable processes the files automatically — validating, transforming, and loading the data into your dedicated dataset. Your data is stored in isolation on a dedicated, secure directory.
Before you begin, make sure you have:
Cable uses SSH public key authentication for SFTP connections.
If you don’t already have an SSH key pair for this integration, generate one:
This creates two files:
~/.ssh/cable_sftp — your private key (keep this secret, never share it)~/.ssh/cable_sftp.pub — your public key (share this with Cable)We recommend Ed25519 keys for their security and performance. If your systems require RSA, use at least 4096 bits: ssh-keygen -t rsa -b 4096 -C "yourorg-cable-sftp" -f ~/.ssh/cable_sftp
Send the contents of your public key file to your Cable point of contact:
The output looks like: ssh-ed25519 AAAA... yourorg-cable-sftp
Never share your private key. Only share the .pub file. If you suspect your private key has been compromised, generate a new key pair immediately and notify your Cable point of contact.
Your Cable point of contact will provide:
A successful connection shows the sftp> prompt. Type exit to disconnect.
On your first connection, your SFTP client will prompt you to verify the server’s host key fingerprint. Contact your Cable point of contact to confirm the fingerprint matches before accepting. This protects against man-in-the-middle attacks.
After verifying the host key once, your client stores it in ~/.ssh/known_hosts. Future connections will verify automatically. If the key changes unexpectedly, your client will warn you — contact Cable before proceeding.
Cable accepts CSV files with the following requirements:
Use descriptive filenames that include the data type and date:
Zip files are not supported. Upload CSV files individually. If you have multiple files, upload them one at a time or use your SFTP client’s batch upload feature.
Upload files directly to your SFTP root directory, or organise them into subdirectories if instructed by your Cable point of contact. Your Cable contact will confirm the expected folder structure during onboarding.
If your security policy requires file-level encryption in addition to SSH transport encryption, you can PGP-encrypt your files before uploading. Cable will automatically detect and decrypt PGP-encrypted files.
.pgp file via SFTP (Cable strips the .pgp extension after decryption)PGP encryption is optional. Cable’s SFTP server uses SSH for transport encryption and your data is stored in isolation. PGP adds an additional layer of encryption for the file contents at rest.
Connect to the SFTP server and upload your files:
For batch uploads, you can use mput or script the upload:
After uploading, contact your Cable point of contact to confirm the files were received and processed successfully.
After upload, Cable automatically:
Your Cable point of contact will confirm when data appears in your dataset and walk you through the available assurance checks.
If Cable cannot process a file (for example, due to encoding errors or missing headers), your Cable point of contact will notify you with details about the issue so you can correct and re-upload.
Once your integration is tested and working, you can automate file delivery using any SFTP client or scheduled job:
Ensure your automation uses the same SSH key and targets the correct hostname and username.
Cable deduplicates data during processing. Re-uploading a file will not create duplicate records in your dataset.
Re-upload the file. Cable processes complete files only — partial uploads are ignored.
There is no hard limit, but files over 1 GB may take longer to process. If you regularly produce very large files, talk to your Cable point of contact about splitting them into smaller batches.
Yes. You can connect from any system that has your SSH private key. Use the same username and key pair for all connections.
Upload a new file with the corrected data and notify your Cable point of contact.