TABLE OF CONTENTS
Summary
Clutch supports two methods for delivering data and documents to your credit union:
API delivery (recommended)
SFTP delivery
In most cases, API delivery is the preferred approach because it offers greater flexibility, faster access to data, and lower operational overhead.
SFTP is still supported, but is typically used only when API integration is not feasible.
Recommendation
We recommend using API delivery whenever possible.
API delivery provides:
On-demand access to data
Easier recovery if data is missed
Faster onboarding and simpler setup
Lower long-term maintenance
SFTP should only be used if:
Your institution cannot support API integration, or
You have strict requirements for file-based delivery
API Delivery
How it works
With API delivery, your team retrieves data directly from Clutch using secure API endpoints.
This is an active model, meaning your system can request data whenever needed.
Benefits
On-demand access
Retrieve data at any time
No dependency on daily file drops
Self-service recovery
Re-fetch data without submitting a support request
No delays if data is missed
Access to historical data
Pull past data directly through the API
No need to involve Clutch support
Simpler setup
No VPN or firewall configuration required
No user or credential provisioning for file transfer
Lower operational overhead
Eliminates manual file handling
Reduces dependency on support teams
Faster onboarding
Integration is lightweight and typically script-based
Clutch provides a ready-to-use script to accelerate setup
Considerations
Requires minimal development effort to call the API
Your team will need to set up a process to retrieve data
SFTP Delivery
How it works
With SFTP delivery, Clutch sends data files to your SFTP server on a scheduled basis (typically once per day).
This is a passive model, meaning your system receives files rather than requesting them.
Benefits
Low upfront effort
No API integration required
Works with existing SFTP workflows
Familiar approach
Many institutions already use SFTP for file ingestion
Considerations
Limited delivery frequency
Files are delivered on a fixed schedule (typically daily)
No ability to retrieve data on demand
No self-service recovery
Missing files require a support request
Recovery may take time
Higher setup complexity
Requires VPN configuration
Firewall rules must be configured
SFTP users and access must be managed
Ongoing maintenance
Changes to credentials, IPs, or firewall rules can disrupt delivery
Requires coordination across teams
Final Note
Both options are supported, but API delivery is the most scalable and reliable approach for ongoing operations.
Your Clutch team can help guide your implementation based on your institution’s technical capabilities and requirements.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article