AG · Secure file exchange

SFTP Access Information

Connection details, authentication requirements, and directory layout

Connection details

Hostsftp.example.com
Port22 (SFTP over SSH)
Production accountag_prod
Acceptance accountag_dev
ProtocolSFTP (not FTP / FTPS)
AuthenticationSSH public-key authentication only

Authentication & access

  • Password login is disabled.
  • Production and acceptance use separate accounts and separate SSH keys.
  • Send us the public key for each environment through an agreed secure channel. Never send a private key.
  • Access is restricted to approved source IP addresses; please provide AG's outbound public IP address(es).
  • Your account is chrooted: you will only see the directories listed below.
Important: Keep production and acceptance credentials separate. Do not reuse a key between environments.

Directory layout

The following paths are relative to your SFTP root (/). You cannot browse outside your assigned environment tree.

/
├── rcv-receipt/
│   ├── out/       # We write; AG collects
│   ├── archive/   # Completed files
│   └── error/     # Failed files
├── rcv-shipment/
│   ├── out/       # We write; AG collects
│   ├── archive/
│   └── error/
├── snd-receipt/
│   ├── in/        # AG writes; we collect
│   ├── archive/
│   └── error/
└── snd-shipment/
    ├── in/        # AG writes; we collect
    ├── archive/
    └── error/

Message types & direction

DirectoryWritten byCollected by
rcv-receipt/outOur systemAG
rcv-shipment/outOur systemAG
snd-receipt/inAGOur system
snd-shipment/inAGOur system

Each message-type directory has its own archive/ and error/ subdirectories.

File handling requirements

  • Atomic writes: upload to a temporary filename, then rename to the final filename when the transfer is complete.
  • File naming: message type, document number, and timestamp. Please confirm if AG already has a standard convention.
  • Archive retention: files are retained in archive/ for 90 days, then purged.
  • Backups: the transfer tree is backed up daily.

Contact for problems

If you cannot connect, authenticate, upload, or collect files, contact:

Team: Integration / Technical Support

Email: support@example.com

Phone: [phone number, if applicable]

Support hours: [business hours and time zone]

When reporting an issue, include the environment (production or acceptance), account name, timestamp with time zone, and error message. Never include a private key or password.