Deprecated - External Bridge (You Build)
This section is deprecated. A replacement solution/specification for externally controlled integration is in active development.
Overview
The External Integration Bridge enables vendors to manage their own integration bridge code for MSPCentric environments, providing an alternative to MSPCentric managed integrations.
In this walkthrough you will learn the key steps to creating an integration.
Prerequisites
- You are able to create an Organization and User using the oem-api.
External Integration Overview
What are External Integrations?
External integrations allow vendors to manage their own integration bridge code for MSPCentric environments, providing an alternative to MSPC managed and hosted integrations. Instead of MSPC hosting and managing your integration bridge, you run your own integration code and interact with MSPC through our Vendor-API API endpoints. This is the same API used by MSPC managed integrations for maximum parity.
Key Benefits
- Full Control: Manage your own integration infrastructure and deployment schedule
- Flexible Architecture: Use any technology stack that can make HTTP requests
Integration Types
The system supports two distinct integration approaches:
| Feature | Custom Hosted | External |
|---|---|---|
| Infrastructure | MSPC-managed | Vendor-managed |
| Authentication | Manual token exchange / Automated | Automated |
| Data Flow | MSPC-Bridge → API | Direct API calls |
| Deployment | MSPC controls | Vendor controls |
| Scalability | MSPC-defined | Vendor-defined |
Core Concepts
Vendor Token
A token generated by MSPC that represents half of the authentication credentials needed for user operations. Combine with your Vendor Token to create a MSPC Token. This token is linked the Vendor entity representing the integration and is delivered alongside your OAuth credentials.
Partner Token
A token generated by MSPC that represents half of the authentication credentials needed for user operations. Combined with your Vendor Token to create a MSPC Token.
MSPC Token
The combined authentication token created by concatenating your Vendor Token with a Partner Token. This token provides access to enhanced Vendor API endpoints.
Integration Status
External integrations use a status system:
- inactive: Authenticated but no properties retrieved
- pending: Properties retrieved, ready for mapping
- connected: Successfully synced unit counts, fully operational
Property Mapping
The process of mapping vendor-specific data structures to MSPC's standardized account and service models.
Getting Started
Ready to implement an external integration? Continue to the Authentication Guide to learn about the Partner Token flow, or jump to the Integration Workflow for a complete implementation guide.