Integrate your application using our SDKs
1 - Choose the right SDK
You've decided to move forward. Great! Now is time to choose how you're going to integrate, especially which SDK you're going to use.
We've got four SDKs available so far, all available on Github
- Integrate with Ruby and RoR
- Integrate with .NET
- Integrate with Java
- Integrate with PHP
- SDK free integration
Our SDKs are the best way to integrate with us, especially when it comes to Single Sign-On which - like any SSO protocol - tends to be a little bit..."hairy" to integrate without any out-of-the-box libraries.
Not the SDK you want? You can always revert to doing an SDK-free integration (see: SDK free integration)
2 - Read the documentation
All the technical details to help you with your integration via the developer platform, using the SDKs, is in the SDKs READ-ME.
The applications have the ability to share data with other applications via a single connector. Connec!™ Data Sharing defines a universal data model that developers can adopt to seamlessly communicate with tens of applications without worrying about the specifics of each of them. Our data model covers financial, customer/supplier, event, payroll, inventory data and more! We're extending it every month!
Each of our SDK includes a pre-configured Connec!™ http client allowing you to make requests without worrying about authentication, endpoint configuration etc. Documentation on how to use the client is available on each SDK documentation (on Github).
Data sharing without real time is lame. That's why Connec!™ also allows you to configure Webhooks so you get notified every time something gets changed in any other application. Documentation about webhooks is also available on each SDK documentation (Github).
3 - Explore the Sample Apps
Our engineering team has developed sample applications for each of the SDKs we propose. These open source apps are a great way to see our APIs in action and understand the scope of the integration. It's also a good way for our engineering team to provide code samples when you need to cover specific scenarios.