There are several scenarios where it might not make sense to work with Edlink, particularly if your needs don't align with the platform's core offerings:
- Deep Integrations for Specific Systems: Edlink is not ideal for building very deep integrations with a single system. If your aim is to create a comprehensive, specialized integration with the full features of a specific platform like Canvas (e.g., accessing their blogs and wikis), using Edlink may not be the best fit.
- Highly Customized Integrations: If a company is looking to ingest every single piece of information from a single platform (e.g. to train artificial intelligence), our broad-based integration model may not support the desired type of interaction.
- Proprietary Feature Needs: If you need access to certain proprietary features of systems that Edlink doesn't support or cover, particularly if you want these features for a specific use case, it might make more sense to build that integration directly. For data security & privacy reasons, Edlink does not allow you to make "pass-through" API calls to school systems.
- Simple, One-Off Integration Needs: If your project only requires integration with a single data provider and you have no plans to expand to other platforms, it might be more efficient to build a direct integration with that system.