Plan your integration
An integration has a business track and a technical track, and the business track usually takes longer than teams expect. You can start both at once to ensure a quicker integration launch timeline.
Contracts and NDAs
Snapdocs requires an mNDA and a structured contract before an integration goes to production. These can be individual contracts between the parties or a tri-party contract. Contract work can delay development, so plan for it early. Your existing customer contract may suffice, for existing customers. APIs are available to current customers.
- Integration partners (LOS, POS, and platform vendors): contact your partner representative or bdteam@snapdocs.com.
- Customers: contact your customer success manager, account executive, or salesteam@snapdocs.com.
What Snapdocs provides
While the agreements are in progress, Snapdocs sets up a development environment for you:
- A non-production environment with API keys and one admin user, who invites the rest of your team. Hosts are listed in Environments and base URLs.
- For integration partners, an integrator account and one test-lender configuration to build against.
Larger builds, such as an integration with a proprietary LOS, may also get some of these:
- (optional) A shared Slack channel for technical questions.
- (optional) A weekly meeting to work through blockers.
- (optional) An implementation manager.
- (optional) A Snapdocs review of your certification results.
What you provide
- Logins to a non-production copy of your system, so Snapdocs can troubleshoot and sign off on workflows before a production release.
- Test transactions ready to work with. For an LOS integration, that means sample loans, including some in the clear-to-close state.
- A completed certification: every scenario on the certification sheet, run from your integrated environment before you go to production.
Scope in phases
Ship the integration in phases as it reaches workflow milestones rather than holding everything for one release. Each product's guides describe its workflows and which ones make a minimal integration; for an LOS building against eClose, LOS integration scope lays out the recommended phasing.